[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Reboots?

From: Marcus Brinkmann
Subject: Re: Reboots?
Date: Tue, 3 Apr 2001 00:15:00 +0200
User-agent: Mutt/1.3.15i

On Sun, Apr 01, 2001 at 06:14:27PM -0400, Roland McGrath wrote:
> > I thought of something verifying that the stack is ok. I don't have any
> > concrete ideas, though.
> In the general case there isn't really anything to do but unwind the stack
> (i.e. have it return all the way up to the thread's root function) and see
> that there is no clobberation.  In the case of request threads, the stack
> is not very deep and should look the same in every thread.  So you could
> probably come up with some kludges for this particular case to check the
> stack for what it ought to contain.

When in gdb after the crash, can I somehow figure out what the memory area
looks like which contains the stack? I'd like to look at the surrounding few
kilobytes. Maybe the amount and content of wrong data provides some data
points (like, a memory page of zeros would give a different impression than
a small sequence of small integers). I can figure out how to dump memory
ranges, but I don't know how to get the address of the stack (and I wonder
if it wouldbe still valid after the crash. gdb info doc has something about
a frame pointer register, which would likely be damaged. Maybe one can go
the chain down from the main frame, or so? I really don't know).
I would like to get an idea of the amount of corruption going on at a very
low (binary data) level, if feasible.


`Rhubarb is no Egyptian god.' Debian http://www.debian.org brinkmd@debian.org
Marcus Brinkmann              GNU    http://www.gnu.org    marcus@gnu.org

reply via email to

[Prev in Thread] Current Thread [Next in Thread]