[ardour-users] ardour2 crashing while removing a bus

[Dragan Noveski]

hi,
i think that i did exactly as you mentioned, but the last, typing

"thread apply all bt" i het only the following output:

Gtk-Message: ./ardour2_ui.rc:83: failed to retrieve property `GtkWidget::cursor-color' of type `GdkColor' from rc file value "((GString*) 0x8c91b20)" of type `GString'

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1236302144 (LWP 6433)]
0xb6aaf2e0 in free () from /lib/tls/libc.so.6
(gdb) 
(gdb) 
(gdb) 
(gdb) 
(gdb) thread apply all bt
Couldn't get registers: Kein passender Prozess gefunden.
(gdb) 
(gdb) thread apply all bt
Couldn't get registers: Kein passender Prozess gefunden.
(gdb) 
Couldn't get registers: Kein passender Prozess gefunden.
(gdb) 
Couldn't get registers: Kein passender Prozess gefunden.
(gdb) 


"...no prozess found.." in german.

what do you think about?

regards,
doc
Sampo Savolainen wrote:

>On Mon, 2006-05-29 at 14:35 +0200, Dragan Noveski wrote:
>  
>
>>sorry, we have to exercise this little more slowly!
>>
>>    
>>
>>>Can you provide us a backtrace of where ardour crashes? You need to compile
>>>a debug version of ardour (scons DEBUG=1, no need to install it though).
>>> 
>>>
>>>      
>>>
>>so, using the old sorcec, runing scons DEBUG=1, not runing scons -c 
>>first and scons install after?
>>    
>>
>
>scons is a lot more clever than make ever was. You don't need to do
>scons -c . Not in this case and not in almost any case.
>
>  
>
>>>Then run ardour in gdb usign the "ardbg" script in ardour2/gtk2_ardour/ 
>>>
>>>      
>>>
>>... so i cd into source-tree /ardour2/gtk2_ardour/ and run ./ardbg?
>>does that means "runing in dgb"?
>>    
>>
>
>Exactly.
>
>  
>
>>>and
>>>giving gdb the magic command "thread apply all bt" after the crash happens.
>>> 
>>>
>>>      
>>>
>>this is too much for me, can you try to explain with other words please.
>>sorry i never used gdb before.
>>    
>>
>
>After you've ran ./ardbg you will get a prompt like so:
>(gdb) 
>
>You need to issue the command "run" to start ardour. You can also give
>parameters to "run" which will be given to ardour at startup, so:
> run /foo/bar/session
>in gdb, is equivalent to running ardour
> ardour /foo/bar/session
>
>After issuing "run" ardour will start. Then duplicate the issue so that
>ardour will crash. Instead of crashing, gdb will stop ardour at the
>point of failure and return you to the gdb prompt (gdb).
>
>At that stage, you need to give the command "thread apply all bt" which
>will give a backtrace of all the threads. You might need to press enter
>many times because gdb stops the output at each full page. After you
>have all the pages (gdb returns to the prompt), copy the backtrace and
>post it here.
>
>  
>