[ardour-users] ardourvst crashes while using stretch/shrink tool

[Dragan Noveski]

Paul Davis wrote:
> On Mon, 2007-01-08 at 20:18 +0100, Dragan Noveski wrote:
>   
>> hi to the list,
>> months ago ardourvst was crashing here while i tried to use the 
>> shrink/stretch tool.
>> later i did not experienced this problem anymore, but with the newest 
>> svn, it is there again.
>>
>> my problem is that running ./ardbg does not work for me anymore, even i 
>> exercised  this allready.
>>     
>
> you cannot use gdb on ardourvst. its not possible. the executable that
> you run is being run inside of wine.
>
> you should use ulimit -c unlimited to allow core dumps, then force a
> crash, then inspect the core dump in ways that i can explain once you've
> got it.
>
>
>
>   
ok, i think that i  got it:

-starting jackd without realtime,
-starting ardourvst in xterm like:

    LANG=en_US.UTF-8 /usr/bin/ardourvst,

-opening new session, one stereo channel, importing a 2sec wav file,

-choosing the shrink/stretch tool, clicking at the region and making a 
"range" where the region should be stretched/shrinked,

-the dialog appears, i choose stretch/shrink it, ardourvst crashes,

-in my homedir i get the "core.3746" file.

-now i cd into gtk2_ardour, typing:

       ../gtk2_ardour$ ./ardbg /home/nowhiskey/core.3746, i become:


GNU gdb 6.4.90-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain 
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as 
"i486-linux-gnu"...gtk2_ardour/ardour-2.0beta10: Datei oder Verzeichnis 
nicht gefunden.

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
Core was generated by 
`/usr/lib/ardour2/ardour_vst.exe.so                                            
'.
Program terminated with signal 11, Segmentation fault.
#0  0x7efd45c6 in ?? ()
(gdb)

and than finaly:

(gdb) thread apply all bt

Thread 9 (process 3746):
#0  0xb7d6a819 in ?? ()

Thread 8 (process 3750):
#0  0xb7d6a819 in ?? ()

Thread 7 (process 3751):
#0  0xb7de5411 in ?? ()

Thread 6 (process 3753):
#0  0xb7de5b3c in ?? ()

Thread 5 (process 3755):
#0  0xb7d6a819 in ?? ()

Thread 4 (process 3756):
#0  0xb7d6a819 in ?? ()

Thread 3 (process 3757):
#0  0xb7d6a819 in ?? ()

Thread 2 (process 3758):
#0  0xb7d6a819 in ?? ()

Thread 1 (process 3760):
#0  0x7efd45c6 in ?? ()
(gdb)



that is all in this case, not lot of pages to paste here!
i hope it is kind of useful for you, if not, and if you have another 
suggestion, please let me know.


cheers,
doc