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 22:09:00 -0000 [thread overview]
Message-ID: <20040622210556.3556C4B104@berman.michael-chastain.com> (raw)
Hi Tao,
It sounds like, perhaps, you are placing the breakpoint first,
and then copying the code on top of the location of the breakpoint.
The way gdb sets breakpoints (usually) is that gdb writes a BREAKPOINT
instruction into the memory at the address indicated. So if you
set a breakpoint first, then overwrite that memory with your own
contents, then you will overwrite the BREAKPOINT instruction and
lose it.
Can you capture a complete gdb session with the 'script' command
and mail it in?
Michael C
GDB QA Guy
next reply other threads:[~2004-06-22 22:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-22 22:09 Michael Elizabeth Chastain [this message]
2004-06-22 22:23 ` Tao Zhang
2004-06-23 5:03 ` Jim Blandy
-- strict thread matches above, loose matches on Subject: below --
2004-06-22 23:17 Michael Elizabeth Chastain
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=20040622210556.3556C4B104@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