[PD] [PD-announce] pd 0.48-0test1 released

Max abonnements at revolwear.com
Tue Jul 18 18:20:35 CEST 2017


On 2017년 07월 18일 17:53, Dan Wilcox wrote:
> I would do a rebuild with debug enabled and then run it through gdb to 
> see where the crash is happening:
> 
> make clean
make: *** No rule to make target 'clean'.  Stop.

> ./configure --enable-debug --enable-jack
> make
> cd bin
> gdb ./pd

Starting program: /home/max/Code/pd-0.48-0test1a/bin/pd
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff7f32700 (LWP 28486)]
[New Thread 0x7ffff7eb1700 (LWP 28488)]

Thread 3 "pd" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff7eb1700 (LWP 28488)]
0x00007ffff78b8f96 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0
(gdb) watchdog: signaling pd...


> Basic instructions are here: 
> http://unknownroad.com/rtfm/gdbtut/gdbsegfault.html
> 
> What we need is the stack trace to see which functions are begin called 
> before the crash.

is it the above?





More information about the Pd-list mailing list