lee wrote: > > Also, I would appreciate if you could run the > > above program on your Etch system and let me know if you can get a > > meaningful bt. > > This is on testing: > [...] > (gdb) backtrace > #0 0xb7fd7424 in __kernel_vsyscall () > #1 0xb7faea71 in pause () from /lib/i686/cmov/libpthread.so.0 > #2 0x08048510 in main () > (gdb) > > Is that meaningful?
Thanks for helping. That is the bt from the first thread. You can get from the others with something like: (gdb) thread apply all bt But on testing it works for me, too. I was asking etch. In the meantime, I found this after some more googling: http://www.mail-archive.com/[EMAIL PROTECTED]/msg313660.html It seems to be a known libc bug for which the fix didn't make it Etch. If anyone knows a workaround, please let me know. Tudor -- Tudor Golubenco http://golubenco.org Beware of bugs in the above code; I have only proved it correct, not tried it. -- Donald Knuth -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]