public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "edwintorok at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/11094] cannot reexecute programs using the GDB JIT interface in shared libs
Date: Tue, 22 Dec 2009 17:00:00 -0000	[thread overview]
Message-ID: <20091222170023.23639.qmail@sourceware.org> (raw)
In-Reply-To: <20091215210108.11094.edwintorok@gmail.com>


------- Additional Comments From edwintorok at gmail dot com  2009-12-22 17:00 -------
(In reply to comment #5)
> Note that GDB turns off ASLR by default:
> 
> gdb64-cvs -nx -ex 'show disable-randomization' -ex 'quit'
> GNU gdb (GDB) 7.0.50.20091211-cvs
> ...
> This GDB was configured as "x86_64-unknown-linux-gnu".
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>.
> Disabling randomization of debuggee's virtual address space is on.
> 

Same here.

I think it tries to set the breakpoint too early, before the shared lib is loaded.

First run:
(gdb) b main
Breakpoint 1 at 0x4005f8: file bp_minus4.c, line 4.
(gdb) r
Starting program: /home/edwin/gdbbug/bp_minus4

Breakpoint 1, main () at bp_minus4.c:4
4           return foo();
(gdb) info sharedlibrary
>From                To                  Syms Read   Shared Object Library
0x000000381da00af0  0x000000381da16a24  Yes (*)     /lib64/ld-linux-x86-64.so.2
0x00007ffff7dfa510  0x00007ffff7dfa628  Yes         ./shared.so
0x000000381de1e730  0x000000381df0292c  Yes (*)     /lib/libc.so.6
(*): Shared library is missing debugging information.

Second run:
(gdb) r
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: /home/edwin/gdbbug/bp_minus4
Warning:
Cannot insert breakpoint -2.
Error accessing memory address 0x7ffff7dfa5dc: Input/output error.

(gdb) info sharedlibrary
>From                To                  Syms Read   Shared Object Library
0x000000381da00af0  0x000000381da16a24  Yes (*)     /lib64/ld-linux-x86-64.so.2
(*): Shared library is missing debugging information.

And here is /proc/maps for the process
$ ps aux|grep gdb
edwin    10001  0.2  0.2  37260 10264 pts/1    S+   18:58   0:00 gdb ./bp_minus4
edwin    10020  0.0  0.0    220    24 pts/1    T    18:59   0:00
/home/edwin/gdbbug/bp_minus4
edwin    10033  0.0  0.0   7288   784 pts/2    S+   18:59   0:00 grep gdb

$ cat /proc/10020/maps
00400000-00401000 r-xp 00000000 fd:02 5389238                           
/home/edwin/gdbbug/bp_minus4
00600000-00601000 rw-p 00000000 fd:02 5389238                           
/home/edwin/gdbbug/bp_minus4
381da00000-381da1d000 r-xp 00000000 09:03 260632                        
/lib/ld-2.10.2.so
381dc1c000-381dc1e000 rw-p 0001c000 09:03 260632                        
/lib/ld-2.10.2.so
7ffff7ffe000-7ffff7fff000 r-xp 00000000 00:00 0                          [vdso]
7ffffffea000-7ffffffff000 rw-p 00000000 00:00 0                          [stack]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                  [vsyscall]

-- 


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

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2009-12-22 17:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-15 21:01 [Bug breakpoints/11094] New: " edwintorok at gmail dot com
2009-12-15 21:01 ` [Bug breakpoints/11094] " edwintorok at gmail dot com
2009-12-15 21:02 ` edwintorok at gmail dot com
2009-12-15 21:03 ` edwintorok at gmail dot com
2009-12-22 14:14 ` edwintorok at gmail dot com
2009-12-22 16:33 ` ppluzhnikov at google dot com
2009-12-22 17:00 ` edwintorok at gmail dot com [this message]
2009-12-22 23:39 ` ppluzhnikov at google dot com
2010-02-20 21:33 ` reid dot kleckner at gmail dot com
2010-02-20 21:47 ` reid dot kleckner at gmail dot com
2010-03-21 20:39 ` edwintorok at gmail dot com
2010-03-22 17:37 ` tromey at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091222170023.23639.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).