Main • ReportingBugs
Developers -> Reporting bugs
On this page:
Bugs or missing features are always possible in any software or other branches of engineering. We will try to fix the problems in Yate as soon as possible. Please note that our priorities may be different than yours...
Even if you spent time and accumulated frustration trying to fix a problem you should always make a good report of the problem. Try to make it brief, informative and correct. It never makes sense to just say "It doesn't work!" - that is not going to get problems fixed or even investigated.
What to check before reporting?
What to include in the report?
Please do NOT include large log files. Also never include core files - they are useless without the executable that crashed and all its libraries and modules.
Do not use screen or telnet captures from rmanager. Some scripts and third party libraries write only to the log file and you may be missing important information if you take it from other sources. Only log file or console information is complete.
Crashes caused by memory corruptions leave useless core files (since the damage was caused earlier, typically by a different thread). If you see "glibc detected ... memory corruption" then please do not post such backtraces. The logs may provide some information about what went wrong.
NOTE!!! A backtrace is usefull only if it includes symbol information. You can compile the debug version of Yate, either by "make debug" or choosing the "Win32 Debug" configuration (in Windows).
Where to report bugs?
How to create a comprehensive backtrace from a core file
echo -e 'thread apply all bt\nquit' > gdb-bt-all.txt gdb -x gdb-bt-all.txt yate coreFILENAME &> yate-bt-all.log
Replace coreFILENAME with the name of the generated core file. The yate-bt-all.log file will contain a backtrace of all threads. For best results Yate should be compiled with debug symbols. This does not hit the performance or memory usage, just increase the size of the files on disk.
Recent versions of Yate provide a readily made gdb-bt-all.txt in the tools subdirectory of sources.
If you have a core dump but Yate was compiled without symbols you can recompile it and get a proper backtrace - just be sure you don't change the source or configure options. Issuing a "make clean debug" will recreate all binaries with exactly the same addresses but with debugging information. Do not use "make ddebug" or "make xdebug" as these will change the code.
Creating core files
04 May 2011:
12 Apr 2011:
9 Mar 2011:
20 Dec 2010:
3 May 2010:
8 March 2010:
6 Aug 2008:
4 Aug 2008: