[NTLUG:Discuss] Segfault Help Needed
George Lass
george.lass at sbcglobal.net
Wed Jun 30 10:47:56 CDT 2010
I have an application that has recently starting segfault'ing and am having problems trying to track down the problem. All of the segfaults have the same "rip" address so I'm fairly sure it is a programming error and not a hardware issue with the server:
Jun 25 16:25:20 philahost-a kernel: smengine[25103]: segfault at 00000000ff839000 rip 0000000055741760 rsp 00000000ff836f28 error 6
Jun 26 01:50:42 philahost-a kernel: smengine[25533]: segfault at 00000000ffb73000 rip 0000000055741760 rsp 00000000ffb71268 error 6
Jun 26 03:50:09 philahost-a kernel: smengine[26872]: segfault at 00000000ffeea000 rip 0000000055741760 rsp 00000000ffee75d8 error 6
Jun 26 07:16:07 philahost-a kernel: smengine[27152]: segfault at 00000000ffbe4000 rip 0000000055741760 rsp 00000000ffbe22d8 error 6
Jun 27 08:16:05 philahost-a kernel: smengine[27636]: segfault at 00000000ffefa000 rip 0000000055741760 rsp 00000000ffef7de8 error 6
Jun 27 16:43:03 philahost-a kernel: smengine[31228]: segfault at 00000000ffa1f000 rip 0000000055741760 rsp 00000000ffa1c108 error 6
Jun 28 07:14:42 philahost-a kernel: smengine[32473]: segfault at 00000000ffa4c000 rip 0000000055741760 rsp 00000000ffa4a138 error 6
If I use objdump to disassemble the executable, the address ranges only go from 0x8049f40 to 0x81f786f, so there must be some load offset that I'm missing. Can anyone point me in the right direction here?
Thanks,
George
More information about the Discuss
mailing list