This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/17846] read memory from _dl_debug_state returns 0xcc instead of 0xf3
- From: "ganzmatthias at hotmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 15 Jan 2015 17:02:13 +0000
- Subject: [Bug gdb/17846] read memory from _dl_debug_state returns 0xcc instead of 0xf3
- Auto-submitted: auto-generated
- References: <bug-17846-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17846
--- Comment #3 from ganzmatthias <ganzmatthias at hotmail dot com> ---
(In reply to Gary Benson from comment #1)
> 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.
> So, when your program is running
> you see 0xCC at that address, but when you stop it you see 0xF3.
So I can not reliably debug programs which read code which may contain
breakpoints (either created by me during the debug session or created by gdb
internaly)?
--
You are receiving this mail because:
You are on the CC list for the bug.