public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "dominik.b.czarnota+bugzilla at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/30616] New: starti in a new inferior halts Date: Wed, 05 Jul 2023 12:04:28 +0000 [thread overview] Message-ID: <bug-30616-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30616 Bug ID: 30616 Summary: starti in a new inferior halts Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: dominik.b.czarnota+bugzilla at gmail dot com Target Milestone: --- When we clone an inferior and execute `starti` in it, GDB halts/freezes. This can be seen in the session below: ``` $ gdb --nx (gdb) file /bin/ls Reading symbols from /bin/ls... (No debugging symbols found in /bin/ls) (gdb) starti Starting program: /usr/bin/ls Program stopped. 0x00007ffff7fe32b0 in _start () from /lib64/ld-linux-x86-64.so.2 (gdb) clone-inferior [New inferior 2] Added inferior 2 on connection 1 (native) (gdb) inferior 2 [Switching to inferior 2 [<null>] (/usr/bin/ls)] (gdb) starti Starting program: /usr/bin/ls ^C <it halted here> ``` The log comes from GDB 12.1 but I believe the same bug exists in GDB >=13. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-07-05 12:04 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-05 12:04 dominik.b.czarnota+bugzilla at gmail dot com [this message] 2023-07-06 22:51 ` [Bug gdb/30616] " 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-30616-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: linkBe 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).