From: Paul Koning <pkoning@equallogic.com>
To: eliz@gnu.org
Cc: yoursindu@gmail.com, dave.korn@artimi.com, gdb@sourceware.org
Subject: Re: Setting registers
Date: Fri, 15 Jun 2007 14:43:00 -0000 [thread overview]
Message-ID: <18034.42274.624904.560657@pkoning.equallogic.com> (raw)
In-Reply-To: <u8xali8r1.fsf@gnu.org>
>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Fri, 15 Jun 2007 18:25:53 +0530 From: Indira
>> <yoursindu@gmail.com> Cc: gdb@sourceware.org
>>
>> Yes I am debuggin a core file. We cant set registers while
>> debuggin a core file?
Eli> No, you can't. The program is dead, all you have is the last
Eli> snapshot of its memory. Even if you could set registers (and
Eli> other variables), it would be of no practical use, since you
Eli> cannot run the program. All you can do is examine its memory
Eli> and call stack.
Sometimes it would be useful to be able to. If the stack is corrupt,
or the return address (for processor types that have such a thing) and
you can figure out the correct values, it would be very handy to be
able to tell gdb "here is the right value" and let it use that for
subsequent analysis.
Right now, that's not possible. So if I have a smashed stack, I have
to walk it by hand -- which means looking at local variables is
essentially undoable. It's not always simply a matter of giving the
right SP to gdb, but often it is.
paul
next prev parent reply other threads:[~2007-06-15 14:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 10:28 Indira
2007-06-13 13:45 ` Dave Korn
2007-06-15 12:55 ` Indira
2007-06-15 14:37 ` Eli Zaretskii
2007-06-15 14:43 ` Paul Koning [this message]
2007-06-15 14:48 ` Daniel Jacobowitz
2007-06-15 15:24 ` Paul Koning
2007-06-15 15:33 ` Daniel Jacobowitz
2007-06-15 16:00 ` Joel Brobecker
2007-06-18 12:01 ` Indira
2007-06-18 12:41 ` Dave Korn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18034.42274.624904.560657@pkoning.equallogic.com \
--to=pkoning@equallogic.com \
--cc=dave.korn@artimi.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=yoursindu@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox