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

2011-10-31 Thread Dallas Clement
back what I find. On Mon, Oct 31, 2011 at 1:53 AM, Chow Loong Jin wrote: > 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

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

2011-10-30 Thread Dallas Clement
0x7f650debe720 (LWP 3784)] 0x7f650c5f7d7c in pthread_join (threadid=190969600, thread_return=0x0) at pthread_join.c:46 On Sun, Oct 30, 2011 at 1:56 AM, Chow Loong Jin wrote: > On 30/10/2011 06:22, Dallas Clement wrote: >> That certainly makes sense.  I'm still not seeing the

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

2011-10-29 Thread Dallas Clement
n ?? () #2 0x7f04e47db695 in ?? () #3 0xe212a700 in ?? () #4 0x7f04e3e73a60 in ?? () #5 0x in ?? () Got any other ideas for me to try? On Sat, Oct 29, 2011 at 4:43 PM, brian m. carlson wrote: > On Sat, Oct 29, 2011 at 02:55:54PM -0500, Dallas Clement wrote: >> How ca

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

2011-10-29 Thread Dallas Clement
OFU 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 Zeimetz                            Debi

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 li

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

Slow signal delivery to server process with heavy I/O

2010-07-10 Thread Dallas Clement
Hi All, I've noticed that asynchronous signals such as SIGINT, SIGTERM etc are delivered to my process long after the signal is sent if the receiving process is handling lots of I/O. My process is a multi-threaded web server. It's got one thread waiting on 'select' to accept incoming connections