From: Tao Zhang <zhangtao@cc.gatech.edu>
To: Andreas Schwab <schwab@suse.de>
Cc: Michael Elizabeth Chastain <mec.gnu@mindspring.com>,
gdb@sources.redhat.com
Subject: Re: Debug code in data section in gdb
Date: Tue, 22 Jun 2004 22:14:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.58.0406221812180.26064@gaia.cc.gatech.edu> (raw)
In-Reply-To: <jezn6vgw7p.fsf@sykes.suse.de>
"doesn't work" means the execution doens't stop at the break points...
-Tao Zhang (zhangtao@cc.gatech.edu)
On Tue, 22 Jun 2004, Andreas Schwab wrote:
> Tao Zhang <zhangtao@cc.gatech.edu> writes:
>
> > Hi, Michael
> >
> > I tried that many times, it doesn't work for me. I even played some trick
> > so that the code buffer is actually placed in code section now. It still
> > doesn't work. I am very confused. The breakpoints work just fine for other
> > code.
>
> Please define "doesn't work". What are the symptoms?
>
> > So break *0x12344657 should work?
>
> Yes. GDB does not distinguish between "code" and "data" section when
> placing a breakpoint, it's all just memory.
>
> Andreas.
>
> --
> Andreas Schwab, SuSE Labs, schwab@suse.de
> SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
> Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
> "And now for something completely different."
>
next prev parent reply other threads:[~2004-06-22 22:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-22 23:17 Michael Elizabeth Chastain
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 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=Pine.GSO.4.58.0406221812180.26064@gaia.cc.gatech.edu \
--to=zhangtao@cc.gatech.edu \
--cc=gdb@sources.redhat.com \
--cc=mec.gnu@mindspring.com \
--cc=schwab@suse.de \
/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