public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/17431] New: follow-exec, "always-inserted on", breakpoints inserted too soon
Date: Wed, 24 Sep 2014 14:57:00 -0000	[thread overview]
Message-ID: <bug-17431-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=17431

            Bug ID: 17431
           Summary: follow-exec, "always-inserted on", breakpoints
                    inserted too soon
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: breakpoints
          Assignee: unassigned at sourceware dot org
          Reporter: palves at redhat dot com

Following an exec with "breakpoint always-inserted on" tries to insert
breakpoints in the image at the addresses the symbols had in the old image.

With "always-inserted off", we see:

gdb testsuite/gdb.multi/multi-arch-exec -ex "set breakpoint always-inserted
off" -ex "cd testsuite"
GNU gdb (GDB) 7.8.50.20140924-cvs
...
(gdb) b main
Breakpoint 1 at 0x400664: file gdb.multi/multi-arch-exec.c, line 24.
                ^^^^^^^^
(gdb) c
The program is not being run.
(gdb) r
Starting program: testsuite/gdb.multi/multi-arch-exec 

Breakpoint 1, main () at gdb/testsuite/gdb.multi/multi-arch-exec.c:24
24        execl (BASEDIR "/multi-arch-exec-hello",
(gdb) c
Continuing.
process 9212 is executing new program:
gdb/testsuite/gdb.multi/multi-arch-exec-hello

Breakpoint 1, main () at gdb/testsuite/gdb.multi/hello.c:40
40        bar();
(gdb) info breakpoints 
Num     Type           Disp Enb Address    What
1       breakpoint     keep y   0x080484e4 in main at
gdb/testsuite/gdb.multi/hello.c:40
                                ^^^^^^^^^^
        breakpoint already hit 2 times
(gdb)


Note how main was 0x400664 in multi-arch-exec, but is 0x080484e4 in
gdb.multi/hello.

With "always-inserted on", we get:

Breakpoint 1, main () at gdb/testsuite/gdb.multi/multi-arch-exec.c:24
24        execl (BASEDIR "/multi-arch-exec-hello",
(gdb) c
Continuing.
infrun: target_wait (-1, status) =
infrun:   9444 [process 9444],
infrun:   status->kind = execd
infrun: infwait_normal_state
infrun: TARGET_WAITKIND_EXECD
Warning:
Cannot insert breakpoint 1.
Cannot access memory at address 0x400664

(gdb)

-- 
You are receiving this mail because:
You are on the CC list for the bug.


             reply	other threads:[~2014-09-24 14:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-24 14:57 palves at redhat dot com [this message]
2014-09-24 14:58 ` [Bug breakpoints/17431] " palves at redhat dot com
2014-09-25 16:32 ` palves at redhat dot com
2014-10-02  9:08 ` cvs-commit at gcc dot gnu.org
2014-10-02 16:14 ` palves 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=bug-17431-4717@http.sourceware.org/bugzilla/ \
    --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).