public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "gbenson at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/17846] read memory from _dl_debug_state returns 0xcc instead of 0xf3
Date: Thu, 15 Jan 2015 16:32:00 -0000 [thread overview]
Message-ID: <bug-17846-4717-pmZa7IGCAE@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17846-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17846
Gary Benson <gbenson at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |gbenson at redhat dot com
Resolution|--- |INVALID
--- Comment #1 from Gary Benson <gbenson at redhat dot com> ---
This is not a bug. GDB implements breakpoints by overwriting whatever is at
the relevant addresses with int3 instructions on x86 when the inferior program
is running. When the inferior stops the int3 instructions are replaced with
whatever was there before. So, when your program is running you see 0xCC at
that address, but when you stop it you see 0xF3.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2015-01-15 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 15:21 [Bug gdb/17846] New: " ganzmatthias at hotmail dot com
2015-01-15 16:32 ` gbenson at redhat dot com [this message]
2015-01-15 16:35 ` [Bug gdb/17846] " palves at redhat dot com
2015-01-15 17:02 ` ganzmatthias at hotmail dot com
2015-01-15 17:33 ` palves at redhat dot com
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=bug-17846-4717-pmZa7IGCAE@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/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).