public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/26652] Unexpected prompt when using "continue" breakpoint commands and mix of -x and -ex Date: Tue, 22 Sep 2020 18:08:23 +0000 [thread overview] Message-ID: <bug-26652-4717-0fqWuJ29WO@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26652-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26652 --- Comment #1 from Simon Marchi <simark at simark dot ca> --- Oops, I hit submit too soon, here's the rest. I have this GDB script: b bar commands print n continue end I run GDB like this: $ ./gdb -nx --data-directory=data-directory ./test -x script -ex r I would expect the breakpoint on bar to be hit twice, then the program to exit. What I see is: $ ./gdb -q -nx --data-directory=data-directory ./test -x script -ex r Reading symbols from ./test... Breakpoint 1 at 0x4004dd: file test.c, line 3. Starting program: /home/smarchi/build/binutils-gdb/gdb/test Breakpoint 1, bar (n=0) at test.c:3 3 } (gdb) And the execution appears to stop here. However, if I then type any command (like print 1), execution appears to resume until the program exits: (gdb) print 1 $1 = 1 $2 = 0 Breakpoint 1, bar (n=1) at test.c:3 3 } $3 = 1 [Inferior 1 (process 29906) exited normally] (gdb) So, it looks like some event gets stuck somewhere and doesn't get pulled by infrun until the event loop is woken up by the command handler. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-09-22 18:08 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-22 18:04 [Bug gdb/26652] New: " simark at simark dot ca 2020-09-22 18:08 ` simark at simark dot ca [this message] 2024-01-05 13:49 ` [Bug gdb/26652] " ssbssa at sourceware dot org 2024-01-05 17:13 ` simon.marchi at polymtl dot ca
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-26652-4717-0fqWuJ29WO@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).