> Is this a known bug?
> I can easily reproduce the segfault.
I think it has been reported before, but it hasn't been investigated. Could
you try to get a stack trace from the fault via gdb?
On Fri, Dec 18, 2009 at 11:46 PM, Doug Cook
>> Is this a known bug?
>> I can easily reproduce the segfault.
> I think it has been reported before, but it hasn't been investigated. Could
> you try to get a stack trace from the fault via gdb?
Here are two. One where the tap_pitch.so is not found and one where it
is found (i had to use the LADSPA_PATH env. variable, configure's
--with-ladspa-path isn't working?).
Debian GNU/Linux (http://www.debian.org)
LACIME: École de technologie supérieure (http://lacime.etsmtl.ca)
Sorry if I wasn't clear. The attached traces don't help very much. By "stack
trace", I mean you use gdb's "backtrace" command to see what function was
running when the crash occurred. If you have a core dump, the syntax is
gdb -q -n -ex bt -batch /usr/local/bin/sox coredumpfilename
If you can't get a core dump, you would use gdb to run sox, then when sox
crashes, you would execute the "bt" or "backtrace" command. Something like:
dcook% gdb sox parameters...