Re: segfault error 4 in libpthread-2.13.so X86_64

2011-10-31 Thread Ben Hutchings
On Mon, Oct 31, 2011 at 02:05:03PM -0500, Dallas Clement wrote: > Just pointing out that I'm seeing a segfault inside pthread_join of > libpthread-2.13.so. I need to look at the pthread source before I can > tell why it crashed. I will also try to roll back to an older version > of this library t

Re: segfault error 4 in libpthread-2.13.so X86_64

2011-10-31 Thread Jonathan Nieder
Dallas Clement wrote: > Will report back what I find. Please don't. This is the wrong list --- it is about development _of_ Debian, not development _on_ Debian. You might find the libc-help list[1] to be more helpful. Or if your questions are Debian-specific, debian-user[2] can be a great help

Re: segfault error 4 in libpthread-2.13.so X86_64

2011-10-31 Thread Dallas Clement
Just pointing out that I'm seeing a segfault inside pthread_join of libpthread-2.13.so. I need to look at the pthread source before I can tell why it crashed. I will also try to roll back to an older version of this library to confirm that I was not seeing this crash earlier. Will report back wha

Re: segfault error 4 in libpthread-2.13.so X86_64

2011-10-30 Thread Chow Loong Jin
On 31/10/2011 13:13, Dallas Clement wrote: > The symbols are definitely present on my system. When I step through > the execution, I can see where it is crashing inside the pthread > library. The last thing it does is join with one thread that was > previously spawned. And so? -- Kind regards,

Re: segfault error 4 in libpthread-2.13.so X86_64

2011-10-30 Thread Dallas Clement
The symbols are definitely present on my system. When I step through the execution, I can see where it is crashing inside the pthread library. The last thing it does is join with one thread that was previously spawned. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7

Re: segfault error 4 in libpthread-2.13.so X86_64

2011-10-29 Thread Chow Loong Jin
On 30/10/2011 06:22, Dallas Clement wrote: > That certainly makes sense. I'm still not seeing the symbols though. > My kernel log show that the segfault came from the pthreads library, > yet when I load the core file into gdb, I'm not seeing any symbols. > > (gdb) bt > #0 0x7f04e3102d7c in ?

Re: segfault error 4 in libpthread-2.13.so X86_64

2011-10-29 Thread Dallas Clement
That certainly makes sense. I'm still not seeing the symbols though. My kernel log show that the segfault came from the pthreads library, yet when I load the core file into gdb, I'm not seeing any symbols. (gdb) bt #0 0x7f04e3102d7c in ?? () #1 0x7f04e3e73a60 in ?? () #2 0x7f04e47d

Re: segfault error 4 in libpthread-2.13.so X86_64

2011-10-29 Thread brian m. carlson
On Sat, Oct 29, 2011 at 02:55:54PM -0500, Dallas Clement wrote: > How can I link with libc6-dbg instead of regular libc6? Thanks. You don't. The files in /usr/lib/debug contain only debugging symbols that have been stripped from the normal binary. You simply link against libc6 as normal and gdb

Re: segfault error 4 in libpthread-2.13.so X86_64

2011-10-29 Thread Dallas Clement
I can see that I've got a debug version of the pthreads library installed on my system. Just don't know how to link with it vs the non-debug version. /usr/lib/debug/lib/x86_64-linux-gnu# ls libpthread-2.13.so On Sat, Oct 29, 2011 at 4:20 PM, Bernd Zeimetz wrote: > Do not use TOFU on Debian list

Re: segfault error 4 in libpthread-2.13.so X86_64

2011-10-29 Thread Bernd Zeimetz
Do not use TOFU on Debian lists. It just makes a mess. On 10/29/2011 09:55 PM, Dallas Clement wrote: > How can I link with libc6-dbg instead of regular libc6? Thanks. http://wiki.debian.org/HowToGetABacktrace -- Bernd ZeimetzDebian GNU/Linux Developer http://bzed.

Re: segfault error 4 in libpthread-2.13.so X86_64

2011-10-29 Thread Dallas Clement
How can I link with libc6-dbg instead of regular libc6? Thanks. On Sat, Oct 29, 2011 at 2:48 PM, Chow Loong Jin wrote: > On 30/10/2011 03:34, Dallas Clement wrote: >> >> I can produce a core file, but unfortunately I can't see the symbols >> inside the pthread lib to determine where it is crashi

Re: segfault error 4 in libpthread-2.13.so X86_64

2011-10-29 Thread Adrian Knoth
On 10/29/11 21:34, Dallas Clement wrote: > Hi All, Hi! > I've got a multi-threaded C++ program that has been working for years > that is segfaulting in the pthread library at exit after upgrading to The "at exit" bit reminds me of a bug the FFADO team has been hunting for months. Feel free to

Re: segfault error 4 in libpthread-2.13.so X86_64

2011-10-29 Thread Chow Loong Jin
On 30/10/2011 03:34, Dallas Clement wrote: > > I can produce a core file, but unfortunately I can't see the symbols > inside the pthread lib to determine where it is crashing. Is there a > pthread library source package or debug version of libc / pthreads > that I can try? Debugging symbols can

segfault error 4 in libpthread-2.13.so X86_64

2011-10-29 Thread Dallas Clement
Hi All, I've got a multi-threaded C++ program that has been working for years that is segfaulting in the pthread library at exit after upgrading to squeeze.  It litters my kernel log with the following message: segfault at 67eaf9d0 ip 7f4568e87d7c sp 7fff4571fe00 error 4 in libpthread-2.1