On Sunday 03 February 2008, Philippe Macaire wrote: > Hi all, > > I have RG crashing after a patch I made, and I would like to inspect > the backtrace with gdb, > but I can't figure out where the core file lies.
If you run from a command line, it should be in . (aka $PWD) if you allow core files to be created. That's not the default state for most distros. From http://rosegarden.sourceforge.net/tutorial/bug-guidelines.html: Producing a Stack Trace If your bug involves a crash, then we will often come back and ask you to produce a stack trace if you didn't include one. In order to produce a useful trace from a standard user environment, you probably need to perform a few steps. Go to a bash prompt (for example, run “Terminal Program (Konsole)” from the KDE menu) and then issue these commands to allow for the creation of core dumps, and to bypass the KDE bug handler: ulimit -c unlimited ulimit -H -c unlimited export KDE_DEBUG=1 Now start rosegarden from this same command line, and reproduce the crash. You should now have a core file in your current directory. The core file is either named "core" or "core.<number>". Now run “gdb” : gdb rosegarden <core_file> Now type “where” at the gdb prompt. Let the trace run to completion (or until it becomes apparent that it's in an infinite loop) and copy the results, then paste them into your report. -- D. Michael McIntyre ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
