This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug breakpoints/10754] New: breakpoints referring to JITted code should be disabled between runs
- From: "vargaz at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: 10 Oct 2009 23:51:04 -0000
- Subject: [Bug breakpoints/10754] New: breakpoints referring to JITted code should be disabled between runs
- Reply-to: sourceware-bugzilla at sourceware dot org
When a breakpoint is placed on a location which is described by a symbol file
registered using the new JIT interface in gdb 7.0, and the program is restarted,
it will fail with a message like:
Warning:
Cannot insert breakpoint 1.
Error accessing memory address 0x40010200: Input/output error.
This is because the breakpoint is resolved to the address of a JITted function
which doesn't exist at the start of the next run.
The attached patch fixes this by disabling breakpoint locations referring to
JITted code between runs. Its against the gdb 7.0 sources. I hope its of
acceptable quality.
--
Summary: breakpoints referring to JITted code should be disabled
between runs
Product: gdb
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: breakpoints
AssignedTo: unassigned at sourceware dot org
ReportedBy: vargaz at gmail dot com
CC: gdb-prs at sourceware dot org
GCC build triplet: x86_64-pc-linux-gnu
GCC host triplet: x86_64-pc-linux-gnu
GCC target triplet: x86_64-pc-linux-gnu
http://sourceware.org/bugzilla/show_bug.cgi?id=10754
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.