Triode wrote: > Don't see a segfault in the logs? As you compilied it yourself can you > run with gdb to find where it crashes?
I recompiled with debugging symbols. Here is what I get when running using gdb [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1". [New Thread 0x40033470 (LWP 2428)] [New Thread 0x4535b470 (LWP 2429)] [Thread 0x4535b470 (LWP 2429) exited] [New Thread 0x40b6e470 (LWP 2430)] [New Thread 0x4535b470 (LWP 2431)] [New Thread 0x40d23470 (LWP 2432)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x40d23470 (LWP 2432)] 0x40bd1760 in mad_layer_III () from /usr/lib/arm-linux-gnueabihf/libmad.so.0 (gdb) backtrace #0 0x40bd1760 in mad_layer_III () from /usr/lib/arm-linux-gnueabihf/libmad.so.0 #1 0x00000000 in ?? () seems like a crash in libmad... I'll try to do additional research unless you have a quick solution? ------------------------------------------------------------------------ sle118's Profile: http://forums.slimdevices.com/member.php?userid=35009 View this thread: http://forums.slimdevices.com/showthread.php?t=97046 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
