This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/15299] Verify breakpoint bytes when removing the breakpoint
- From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Wed, 27 Mar 2013 18:28:14 +0000
- Subject: [Bug gdb/15299] Verify breakpoint bytes when removing the breakpoint
- Auto-submitted: auto-generated
- References: <bug-15299-4717 at http dot sourceware dot org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=15299
--- Comment #10 from Jan Kratochvil <jan.kratochvil at redhat dot com> 2013-03-27 18:28:14 UTC ---
(In reply to comment #9)
> Yes, this is good idea if memory write check is enough, but how can it help if
> the program read from software breakpoint address (integrity check)?
It is never perfect but it should at least improve the situation.
> It behaves differently. If GDB step into another breakpoint, then it rewrite
> breakpoints. See attached. Why?
I do not see exactly what do you want to know.
For example if you have a breakpoint at address X and GDB is currently stopped
at that address X during "continue" the breakpoint at address X is removed,
single-stepped, breakpoint is put back to address X and only then the inferior
is continued. You can see it if you use "set debug infrun 1".
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.