[LCP]debugging a SIGSEGV
Tushar_Oza at Dell.com
Tushar_Oza at Dell.com
Mon Feb 7 08:09:02 UTC 2005
Seems like you may have used a "pthread_atfork" or a similar at fork
registration fucntion which is no longer available and your pointer is
in la-la land!? What kernel are you using, if I may ask!? Also, using
NTPL libraries? Is your program linked with -pthreads?
tushar
-----Original Message-----
From: linuxcprogramming-admin at lists.linux.org.au
[mailto:linuxcprogramming-admin at lists.linux.org.au] On Behalf Of Karthik
Vishwanath
Sent: Sunday, February 06, 2005 1:33 PM
To: C-programming
Subject: [LCP]debugging a SIGSEGV
My program quits _after_ processing the last lines of main() with a
SIGSEGV (the last lines of main() are a printf() statements). I compiled
the program using the -ggdb flags and used ddd to execute the program to
get any more info. on where the code dies and heres what ddd tells me:
"Program received signal SIGSEGV, Segmentation fault. 0x4012be5b in
__register_atfork () from /lib/libc.so.6 (gdb) "
Can anyone tell me what is going on, and why this could be happening (I
have checked writes to malloc'd *s very carefully and I don't think its
because of accessing an uninitialized memory location etc.)? Any/all
pointers (no pun intended) toward throwing some light on how to get rid
of the segmentation fault will be very appreciated.
Thanks,
-K
_______________________________________________
This is the Linux C Programming List
: http://lists.linux.org.au/listinfo/linuxcprogramming List
More information about the linuxCprogramming
mailing list