public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug ada/25811] New: [ada] start attempts to set breakpoint on main of previous exec
Date: Fri, 10 Apr 2020 16:33:06 +0000	[thread overview]
Message-ID: <bug-25811-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 25811
           Summary: [ada] start attempts to set breakpoint on main of
                    previous exec
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: ada
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

Consider the execs first and second from test-case gdb.ada/exec_changed.exp.

If we load first, and start it, and then subsequently load and start second:
...
$ gdb -ex "file first" -ex start -ex "file second" -ex start
Reading symbols from first...
Temporary breakpoint 1 at 0x401f88: file exec_changed/first.adb, line 16.
Starting program: /data/gdb_versions/devel/first 

Temporary breakpoint 1, first ()
    at exec_changed/first.adb:16
16      procedure First is
A program is being debugged already.
Are you sure you want to change the file? (y or n) y
Load new symbol table from "second"? (y or n) y
Reading symbols from second...
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Function "_ada_first" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Temporary breakpoint 2 (-qualified _ada_first) pending.
Starting program: /data/gdb_versions/devel/second 
[Inferior 1 (process 1069) exited normally]
...
the second start attempts to set a breakpoint on the main of first, which
fails, after we don't stop at main but just run to exit.

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

             reply	other threads:[~2020-04-10 16:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-10 16:33 vries at gcc dot gnu.org [this message]
2023-04-19 18:40 ` [Bug ada/25811] " tromey at sourceware dot org
2023-08-21 15:41 ` tromey at sourceware dot org
2023-08-23 17:12 ` tromey at sourceware dot org
2023-09-05 16:05 ` cvs-commit at gcc dot gnu.org
2023-09-05 16:06 ` tromey at sourceware dot org

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