Analysing core files
From: grid (prohit99_at_gmail.com)
Date: 11/24/05
- Next message: Alvin: "Library statistics"
- Previous message: Paul Pluzhnikov: "Re: getting memory mapped IO to work on linux"
- Next in thread: Rich Teer: "Re: Analysing core files"
- Reply: Rich Teer: "Re: Analysing core files"
- Reply: Paul Pluzhnikov: "Re: Analysing core files"
- Reply: Argus225: "Re: Analysing core files"
- Reply: Markus Elfring: "Re: Analysing core files"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 24 Nov 2005 20:18:40 +0530
Hi,
I know we can use a debugger to see some details about a core file.I
do a strings on the core file and it prints a lot of information,though
the debugger only shows limited relevant information.
I have a long running program so its difficult to attach to the program
and I even dont know at what point its crashing.Also in the debugger it
shows up as a corrupt stack, like below :
#3 0x20000000017ab4f0 in __pthread_sighandler_rt () from
/lib/libpthread.so.0
#4 <signal handler called>
Previous frame inner to this frame (corrupt stack?)
I was thinking if I can make use of some the details present in the core
file which the debugger dosent inform.
Can anyone help in digging out the wealth of information being left
hidden inside the core file ?
PS: Platform is Linux.
TIA
~
- Next message: Alvin: "Library statistics"
- Previous message: Paul Pluzhnikov: "Re: getting memory mapped IO to work on linux"
- Next in thread: Rich Teer: "Re: Analysing core files"
- Reply: Rich Teer: "Re: Analysing core files"
- Reply: Paul Pluzhnikov: "Re: Analysing core files"
- Reply: Argus225: "Re: Analysing core files"
- Reply: Markus Elfring: "Re: Analysing core files"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|