public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug cli/30498] New: [gdb/cli] GDB stuck in i-search after ^C
@ 2023-05-30 12:07 vries at gcc dot gnu.org
  2023-05-31 13:06 ` [Bug cli/30498] " cvs-commit at gcc dot gnu.org
  0 siblings, 1 reply; 2+ messages in thread
From: vries at gcc dot gnu.org @ 2023-05-30 12:07 UTC (permalink / raw)
  To: gdb-prs

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

            Bug ID: 30498
           Summary: [gdb/cli] GDB stuck in i-search after ^C
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: cli
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

I ran into the following.

Start gdb, type ^R to start reverse-i-search, and type foo, and then ^C to quit
the i-search:
...
$ gdb -q
(failed reverse-i-search)`foo': Quit
(gdb) 
...

So far so good, let's now try to type a command, say file:
...
$ gdb -q
(failed reverse-i-search)`foo': Quit
(failed reverse-i-search)`foofile': 
...
Hmm, it seems like we're stuck in the i-search.

Found relevant discussion here:
https://lists.gnu.org/archive/html/bug-readline/2015-05/msg00014.html .

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [Bug cli/30498] [gdb/cli] GDB stuck in i-search after ^C
  2023-05-30 12:07 [Bug cli/30498] New: [gdb/cli] GDB stuck in i-search after ^C vries at gcc dot gnu.org
@ 2023-05-31 13:06 ` cvs-commit at gcc dot gnu.org
  0 siblings, 0 replies; 2+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2023-05-31 13:06 UTC (permalink / raw)
  To: gdb-prs

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

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=6e9bcaad3fd8f7635afb9fa7013762da2eeff8e5

commit 6e9bcaad3fd8f7635afb9fa7013762da2eeff8e5
Author: Tom de Vries <tdevries@suse.de>
Date:   Wed May 31 15:06:40 2023 +0200

    [gdb/testsuite] Fix gdb.tui/pr30056.exp for native-extended-gdbserver

    When running test-case gdb.tui/pr30056.exp with target board
    native-extended-gdbserver, I run into:
    ...
    Quit^[[K^M^[[B(gdb) PASS: gdb.tui/pr30056.exp: Control-C
    Remote debugging from host ::1, port 38810^M
    ^M(failed reverse-i-search)`xyz': ^M(gdb) target extended-remote \
      localhost:2346^[[7GWARNING: Timed out waiting for EOF in server after \
      monitor exit
    ...

    This is due to the fact that ^C doesn't abort the reverse-i-search.  This
    appears to be due to a readline problem.  A PR is open about this: PR
    cli/30498.

    Add a KFAIL for the PR, and ensure that the isearch is aborted by using ^G,
    such that we have a responsive prompt to handle the "monitor exit" command
    that native-extended-gdbserver issues.

    Tested on x86_64-linux.

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2023-05-31 13:06 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-05-30 12:07 [Bug cli/30498] New: [gdb/cli] GDB stuck in i-search after ^C vries at gcc dot gnu.org
2023-05-31 13:06 ` [Bug cli/30498] " cvs-commit at gcc dot gnu.org

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