From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: mec.gnu@mindspring.com, zhangtao@cc.gatech.edu
Cc: gdb@sources.redhat.com
Subject: Re: Debug code in data section in gdb
Date: Tue, 22 Jun 2004 23:17:00 -0000 [thread overview]
Message-ID: <20040622231735.3CB3A4B104@berman.michael-chastain.com> (raw)
> I can break the program just before the execution jump to the
> code copied from somewhere. Then I set a breakpoint at the beginning of
> the copied code. It still won't work.
That's the right thing to do. It should work.
> Another thing is I see the code is same as the original code. My
> question is whether I can see the GDB modified instruction by
> disassemble the memory ? When and How gdb modifies the instruction?
gdb goes to some lengths to report the original contents of memory
no matter how you examine it.
> I suspect this problem is specific to my port of gdb, so maybe I need to
> understand how breakpoints work in gdb to understand my problem. Could
> anybody give me some pointers to articles or online books on debugger or
> gdb?
Mmmm, start with the gdb internals manual (doc/gdbint.texinfo).
Again, it would help a lot if you could use the 'script' command to
capture an entire gdb session, and then mail in the 'typescript' file.
Michael C
next reply other threads:[~2004-06-22 23:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-22 23:17 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-22 22:09 Michael Elizabeth Chastain
2004-06-22 22:23 ` Tao Zhang
2004-06-23 5:03 ` Jim Blandy
2004-06-22 18:19 Michael Elizabeth Chastain
2004-06-22 19:10 ` Tao Zhang
2004-06-22 20:43 ` Andreas Schwab
2004-06-22 22:14 ` Tao Zhang
2004-06-22 17:36 Tao Zhang
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=20040622231735.3CB3A4B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=gdb@sources.redhat.com \
--cc=zhangtao@cc.gatech.edu \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).