(CC-ed rosegarden-devel. Followups probably belong there)
> Speaking of which, what's the usual way of debugging crash problems with
> rosegarden?
I use gdb to find the crash site itself. Pretty normal: Start RG, attach
gdb to the running process, make the crash, see the backtrace. Of course
you must have configured/compiled RG with --enable-debug.
After that, you can't do the normal thing of setting breakpoints and
stepping thru. Other threads keep running (looks like Jack support),
spewing output complaining that RG is stopped. This tends to confuse the
debugger (maybe just gdb under emacs/gud?) Nevertheless I find gud
indispensable for segregating rg's debug output in a separate window.
What I do then (seems to be the practice here) is primitive: add debug
tracing at the points I need to know about. Recompile. Capture output to
a file, like
./rosegarden &> ../trace
Inspect the trace file (emacs' occur is very helpful). Repeat as needed.
Tom Breton (Tehom)
------------------------------------------------------------------------------
Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS
and more. Get SQL Server skills now (including 2012) with LearnDevNow -
200+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
SALE $99.99 this month only - learn more at:
http://p.sf.net/sfu/learnmore_122512
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
