[ardour-dev] quick crash report

Doug McLain dougmclain at cayf.org
Wed Sep 7 00:38:53 PDT 2005

Sampo Savolainen wrote:
> On Wed, 2005-09-07 at 03:20 -0400, Doug McLain wrote:
>>Wolfgang Woehl wrote:
>>>Reproducable with a new session. With bus and track. No backtrace either 
>>>because the X-lockup *is* hard (ardour/gtk 0.602.0 libardour 0.898.0)
>>>How do you dump core again?
>>ulimit -c unlimited on the shell that you will run ardour from.
> That doesn't help if ardour freezes completely. That means that it
> doesn't exit at all due to a fault which would cause a segmentation
> fault.
> You can get a backtrace by running ardour withing gdb, and stopping the
> application from gdb when ardour is frozen. You can stop ardour by
> pressing CTRL-Z from the gdb console. Then give gdb the magic command
> "thread apply all bt" and send the results here.
> It's also probably a good idea to run jackd without -R and in soft mode,
> so gdb doesn't slow ardour down so much that it would be kicked out of
> jackd.

If its just an X freeze and not a system freeze, and ulimit -c was set, 
and another machine is available on your network (I assume alot, im 
spoiled i guess) you can ssh/telnet in and kill -s 11 <pid of ardour> to 
force a segfault. I take these measures since I never have good luck 
getting very far with ardour running inside gdb.

More information about the Ardour-Dev mailing list