public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug gdb/14585] New: "Error accessing memory address" when creating JIT internal breakpoint
@ 2012-09-14 19:41 sergiodj at redhat dot com
  2012-09-15  4:25 ` [Bug gdb/14585] " sergiodj at redhat dot com
  2012-09-17 18:38 ` tromey at redhat dot com
  0 siblings, 2 replies; 3+ messages in thread
From: sergiodj at redhat dot com @ 2012-09-14 19:41 UTC (permalink / raw)
  To: gdb-prs

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

             Bug #: 14585
           Summary: "Error accessing memory address" when creating JIT
                    internal breakpoint
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
        AssignedTo: unassigned@sourceware.org
        ReportedBy: sergiodj@redhat.com
    Classification: Unclassified


I could not find an easy way to reproduce this bug so far.  The only way I
managed to do so was to:

1) git clone git://git.qemu.org/qemu.git
2) ./configure --enable-kvm --python=python2 --target-list=x86_64-softmmu
--disable-uuid --disable-werror --enable-debug --enable-fdt # you will need to
install the dependencies
3) gdb -q -ex 'run' /tmp/install-qemu/bin/qemu-system-x86_64

And you will see:

Warning:
Cannot insert breakpoint -1.
Error accessing memory address 0x34e96c: Input/output error.

Running git-bisect on gdb.git, I found the culprit as being:

a7262466d02155f5f70422804e5971f8d5e78118 is the first bad commit
commit a7262466d02155f5f70422804e5971f8d5e78118
Author: Tom Tromey <tromey@redhat.com>
Date:   Wed Feb 1 20:21:21 2012 +0000

I spent some hours debugging this problem, and apparently it happens because
the JIT code does not recreate its internal breakpoint (placed on
__jit_debug_register_code) when the inferior is created.  Somehow the
breakpoint address does not get relocated and is invalid when
insert_breakpoint_locations tries to reinsert it.

This happens on x86_64, confirmed on Fedora 17 and ArchLinux.

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


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug gdb/14585] "Error accessing memory address" when creating JIT internal breakpoint
  2012-09-14 19:41 [Bug gdb/14585] New: "Error accessing memory address" when creating JIT internal breakpoint sergiodj at redhat dot com
@ 2012-09-15  4:25 ` sergiodj at redhat dot com
  2012-09-17 18:38 ` tromey at redhat dot com
  1 sibling, 0 replies; 3+ messages in thread
From: sergiodj at redhat dot com @ 2012-09-15  4:25 UTC (permalink / raw)
  To: gdb-prs

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

--- Comment #1 from Sergio Durigan Junior <sergiodj at redhat dot com> 2012-09-15 04:25:41 UTC ---
For the record, the reference to gdb-patches is
http://sourceware.org/ml/gdb-patches/2012-02/msg00023.html

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


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug gdb/14585] "Error accessing memory address" when creating JIT internal breakpoint
  2012-09-14 19:41 [Bug gdb/14585] New: "Error accessing memory address" when creating JIT internal breakpoint sergiodj at redhat dot com
  2012-09-15  4:25 ` [Bug gdb/14585] " sergiodj at redhat dot com
@ 2012-09-17 18:38 ` tromey at redhat dot com
  1 sibling, 0 replies; 3+ messages in thread
From: tromey at redhat dot com @ 2012-09-17 18:38 UTC (permalink / raw)
  To: gdb-prs

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

Tom Tromey <tromey at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |tromey at redhat dot com
         Resolution|                            |DUPLICATE

--- Comment #2 from Tom Tromey <tromey at redhat dot com> 2012-09-17 18:37:46 UTC ---
Maybe not obvious from the symptoms, but this is a dup.

*** This bug has been marked as a duplicate of bug 13987 ***

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


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2012-09-17 18:38 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-09-14 19:41 [Bug gdb/14585] New: "Error accessing memory address" when creating JIT internal breakpoint sergiodj at redhat dot com
2012-09-15  4:25 ` [Bug gdb/14585] " sergiodj at redhat dot com
2012-09-17 18:38 ` tromey at redhat dot com

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