From: Eli Zaretskii via Gdb-patches <gdb-patches@sourceware.org>
To: Hannes Domani <ssbssa@yahoo.de>
Cc: pedro@palves.net, aburgess@redhat.com,
gdb-patches@sourceware.org, brobecker@adacore.com
Subject: Re: GDB 12.0.90 available for testing
Date: Sun, 03 Apr 2022 16:34:48 +0300 [thread overview]
Message-ID: <83h77affyf.fsf@gnu.org> (raw)
In-Reply-To: <1379565857.1750775.1648990951974@mail.yahoo.com> (message from Hannes Domani on Sun, 3 Apr 2022 13:02:31 +0000 (UTC))
> Date: Sun, 3 Apr 2022 13:02:31 +0000 (UTC)
> From: Hannes Domani <ssbssa@yahoo.de>
> Cc: "brobecker@adacore.com" <brobecker@adacore.com>,
> "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
> "pedro@palves.net" <pedro@palves.net>
>
> I just finished my build of gdb 12 branch with a mingw-w64 gcc, and I also have that
> problem when starting gdb with -i=mi:
>
> (gdb)
> r -Q
> &"g\n"
> &"Ambiguous command \"g\": gcore, generate-core-file, goto-bookmark, gr, gu, guile, guile-repl.\n"
> ^error,msg="Ambiguous command \"g\": gcore, generate-core-file, goto-bookmark, gr, gu, guile, guile-repl."
>
>
> If I "delete" that not-visible 'g' with backspace before I enter the command, it works again.
> So there definitely is something weird going on here.
Thanks. It is therefore strange that Joel reported he and others
didn't see this in their MinGW builds.
next prev parent reply other threads:[~2022-04-03 13:35 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-20 5:58 Joel Brobecker via Gdb-patches
2022-03-26 15:26 ` Eli Zaretskii via Gdb-patches
2022-03-26 15:53 ` Joel Brobecker via Gdb-patches
2022-03-26 16:15 ` Eli Zaretskii via Gdb-patches
2022-04-07 16:08 ` Tom Tromey
2022-04-07 16:12 ` Eli Zaretskii via Gdb-patches
2022-04-07 18:00 ` Joel Brobecker via Gdb-patches
2022-04-07 18:04 ` Simon Marchi via Gdb-patches
2022-04-07 19:02 ` Tom Tromey
2022-04-07 19:11 ` Joel Brobecker via Gdb-patches
2022-04-08 13:38 ` Tom Tromey
2022-04-08 14:33 ` Pedro Alves
2022-04-18 15:26 ` Tom Tromey via Gdb-patches
2022-04-18 16:13 ` Tom Tromey via Gdb-patches
2022-04-07 18:30 ` Tom Tromey
2022-04-08 6:58 ` Eli Zaretskii via Gdb-patches
2022-04-18 19:28 ` Tom Tromey via Gdb-patches
2022-03-26 17:59 ` Eli Zaretskii via Gdb-patches
2022-03-26 18:34 ` Eli Zaretskii via Gdb-patches
2022-03-26 18:51 ` Eli Zaretskii via Gdb-patches
2022-03-27 6:27 ` Eli Zaretskii via Gdb-patches
2022-03-31 6:23 ` Eli Zaretskii via Gdb-patches
2022-03-31 9:48 ` Pedro Alves
2022-03-31 11:55 ` Eli Zaretskii via Gdb-patches
2022-04-01 10:12 ` Andrew Burgess via Gdb-patches
2022-04-01 11:18 ` Eli Zaretskii via Gdb-patches
2022-04-01 11:25 ` Eli Zaretskii via Gdb-patches
2022-04-01 15:21 ` Andrew Burgess via Gdb-patches
2022-04-01 16:18 ` Eli Zaretskii via Gdb-patches
2022-04-03 13:02 ` Hannes Domani via Gdb-patches
2022-04-03 13:34 ` Eli Zaretskii via Gdb-patches [this message]
2022-04-03 14:03 ` Joel Brobecker via Gdb-patches
2022-04-03 15:26 ` Hannes Domani via Gdb-patches
2022-04-03 15:38 ` Eli Zaretskii via Gdb-patches
2022-04-07 11:09 ` Eli Zaretskii via Gdb-patches
2022-04-07 18:03 ` Joel Brobecker via Gdb-patches
2022-04-10 19:06 ` Joel Brobecker via Gdb-patches
2022-04-11 11:42 ` Eli Zaretskii via Gdb-patches
2022-04-17 17:28 ` Joel Brobecker via Gdb-patches
2022-04-19 16:12 ` Andrew Burgess via Gdb-patches
2022-04-19 16:16 ` Eli Zaretskii via Gdb-patches
2022-04-20 13:26 ` Andrew Burgess via Gdb-patches
2022-04-20 17:11 ` Joel Brobecker via Gdb-patches
2022-04-20 17:30 ` Eli Zaretskii via Gdb-patches
2022-04-24 15:56 ` Joel Brobecker via Gdb-patches
2022-04-25 8:48 ` Andrew Burgess via Gdb-patches
2022-04-07 18:28 ` Tom Tromey via Gdb-patches
2022-04-07 19:22 ` Pedro Alves
2022-04-08 4:04 ` Eli Zaretskii via Gdb-patches
2022-04-01 12:36 ` Joel Brobecker via Gdb-patches
2022-04-01 12:50 ` Eli Zaretskii via Gdb-patches
2022-04-01 14:12 ` Joel Brobecker via Gdb-patches
2022-04-01 14:27 ` Eli Zaretskii via Gdb-patches
2022-04-01 14:31 ` Joel Brobecker via Gdb-patches
2022-04-08 14:44 ` Pedro Alves
2022-04-08 20:05 ` Eli Zaretskii via Gdb-patches
2022-03-27 9:55 ` Eli Zaretskii via Gdb-patches
2022-03-27 1:55 ` Simon Marchi via Gdb-patches
2022-03-27 5:20 ` Eli Zaretskii via Gdb-patches
2022-04-07 16:13 ` Tom Tromey
2022-04-07 16:39 ` Eli Zaretskii via Gdb-patches
2022-03-31 6:21 ` Eli Zaretskii via Gdb-patches
2022-03-31 9:44 ` Pedro Alves
2022-03-31 11:58 ` Eli Zaretskii via Gdb-patches
2022-03-31 12:05 ` Pedro Alves
2022-03-31 14:00 ` Eli Zaretskii via Gdb-patches
2022-04-12 14:01 ` Luis Machado via Gdb-patches
2022-04-12 17:57 ` Joel Brobecker via Gdb-patches
2022-04-13 7:36 ` Luis Machado via Gdb-patches
2022-04-13 12:19 ` Luis Machado via Gdb-patches
2022-04-13 16:20 ` Jose E. Marchesi via Gdb-patches
2022-04-17 17:33 ` Joel Brobecker via Gdb-patches
2022-04-18 1:48 ` Alan Modra via Gdb-patches
2022-04-26 13:54 ` Luis Machado via Gdb-patches
2022-04-26 14:56 ` Joel Brobecker via Gdb-patches
2022-04-26 15:15 ` Luis Machado via Gdb-patches
2022-04-20 17:33 ` Pedro Alves
2022-04-20 17:52 ` Joel Brobecker via Gdb-patches
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=83h77affyf.fsf@gnu.org \
--to=gdb-patches@sourceware.org \
--cc=aburgess@redhat.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=pedro@palves.net \
--cc=ssbssa@yahoo.de \
/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