Cool!
Analyzing core dump after crash is commonly referred as "post mortem" 
debugging, I'd google that with gdb.
Obtaining a call stack is normally just a command: "backtrace".
It can be tricky with a crash if the stack is corrupted and/or the analyzed 
software is not a debug version.
(Non-debug binaries can contain several optimizations which distorts the call 
stack.) But give it a try.
Also, multi-threaded apps maybe not straight forward either.

http://stackoverflow.com/questions/2652944/how-to-find-which-thread-caused-segfault-in-a-post-mortem-gdb-session
http://codingrelic.geekhold.com/2009/06/post-mortem-debugging-core-files.html

Csaba
________________________________________
From: [email protected] [[email protected]] On Behalf Of 
Howard White [[email protected]]
Sent: Tuesday, September 18, 2012 6:22 PM
To: [email protected]
Subject: Re: [nlug] Yet another plaint from your not so super SysAdmin

On 09/18/2012 01:03 PM, Toth, Csaba wrote:
> Hi Howard,
>
> Another thing. Please don't beat me up with a stick for this, but as a 
> developer I'd try to get the callstack from the crashdump. Even for a non 
> developer it might give a clue about the crash.
> However, you'd need a gdb (GNU debugger) for that, but since you mention that 
> this is a production system, there's a good chance you may not have gdb 
> there. Actually it is better if you don't have: because developer tools could 
> be very handy for a hacker in case of a break-in.
>
> Csaba
>

You do not have to worry about me beating anyone with anything more than
a wet noodle that offers me kind advice in the manner that you present,
Csaba.  I'll give this a spin as our "production" is in fact software
development and gdb is on that machine.

Howard

--
You received this message because you are subscribed to the Google Groups 
"NLUG" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/nlug-talk?hl=en


-- 
You received this message because you are subscribed to the Google Groups 
"NLUG" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/nlug-talk?hl=en

Reply via email to