[ardour-users] ardour 2.0 testing

Paul Davis paul at linuxaudiosystems.com
Wed Jan 18 06:43:32 PST 2006

> the app crashes, it leaves a core file (called either core or core.N,
> where N was the process ID).  Now run gdb on the program you ran and
> the core file: "gdb /usr/bin/ardour core" and type "bt" at the gdb
> prompt.  There's your stack trace.  No need to remember what you did
> to make it crash.

just a reminder: typing "bt" is not useful in a multithreaded
application like ardour. instead, the gdb command is:

	thread apply all bt


More information about the Ardour-Users mailing list