[Bug breakpoints/10754] breakpoints referring to JITted code should be disabled between runs

[Bug breakpoints/10754] breakpoints referring to JITted code should be disabled between runs

[vargaz at gmail dot com]

------- Additional Comments From vargaz at gmail dot com  2009-10-10 23:51 -------
Created an attachment (id=4264)
 --> (http://sourceware.org/bugzilla/attachment.cgi?id=4264&action=view)
patch against gdb 7.0


-- 


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.

[Bug breakpoints/10754] New: breakpoints referring to JITted code should be disabled between runs

[vargaz at gmail dot com]

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.

[Bug breakpoints/10754] breakpoints referring to JITted code should be disabled between runs

[tromey at redhat dot com]

------- Additional Comments From tromey at redhat dot com  2010-02-04 19:37 -------
The best thing to do is submit the patch following the
contribution instructions; see http://sourceware.org/gdb/contribute/
FWIW the idea seems reasonable to me.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at redhat dot com


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.

[Bug breakpoints/10754] breakpoints referring to JITted code should be disabled between runs

[reid dot kleckner at gmail dot com]

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |reid dot kleckner at gmail
                   |                            |dot com


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.

[Bug breakpoints/10754] breakpoints referring to JITted code should be disabled between runs

[hjl.tools at gmail dot com]

http://sourceware.org/bugzilla/show_bug.cgi?id=10754

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hjl.tools at gmail dot com

-- 
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.