From: Hannes Domani <ssbssa@yahoo.de>
To: Andrew Burgess <aburgess@redhat.com>, Eli Zaretskii <eliz@gnu.org>
Cc: "brobecker@adacore.com" <brobecker@adacore.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"pedro@palves.net" <pedro@palves.net>
Subject: Re: GDB 12.0.90 available for testing
Date: Sun, 3 Apr 2022 13:02:31 +0000 (UTC) [thread overview]
Message-ID: <1379565857.1750775.1648990951974@mail.yahoo.com> (raw)
In-Reply-To: <83zgl44w1m.fsf@gnu.org>
Am Freitag, 1. April 2022, 18:18:34 MESZ hat Eli Zaretskii via Gdb-patches <gdb-patches@sourceware.org> Folgendes geschrieben:
> > From: Andrew Burgess <aburgess@redhat.com>
> > Cc: pedro@palves.net, gdb-patches@sourceware.org, brobecker@adacore.com
> > Date: Fri, 01 Apr 2022 16:21:35 +0100
> >
> > >> So I guess there are problems with making the console input stream
> > >> unbuffered, at least on MS-Windows?
> > >
> > > Or maybe read_command_file shouldn't call setbuf for the same stream
> > > repeatedly, but only once?
> >
> > I think it must be the former, as far as I can tell with the patch I
> > posted we call setbuf just once on stdin (for your -i=mi case). The
> > read_command_file will only be called if you have gdbinit files to read
> > in. You could try adding the -nx and -nh options when starting GDB to
> > prevent any gdbinit files being read, but I'd be amazed if that makes a
> > difference.
>
> It indeed doesn't.
>
>
> > Sorry I can't offer more insight.
>
>
> So what would be the way forward? The patch below fixes the problem
> for me. But given that Joel says the problem doesn't happen in your
> MinGW builds, maybe we shouldn't install it, even for MinGW? Or
> condition it only by symbols available in mingw.org's MingW?
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.
Not related, but on my first test with TUI I noticed that a line-break is missing
after the "Load new symbol table" question:
(gdb) file c:/heob/heob64.exe
Load new symbol table from "c:/heob/heob64.exe"? (y or n) yReading symbols from c:/heob/heob64.exe...
(gdb) file c:/heob/heob32.exe
Load new symbol table from "c:/heob/heob32.exe"? (y or n) yReading symbols from c:/heob/heob32.exe...
It's fine outside of TUI:
(gdb) file c:/heob/heob64.exe
Load new symbol table from "c:/heob/heob64.exe"? (y or n) y
Reading symbols from c:/heob/heob64.exe...
(gdb) file c:/heob/heob32.exe
Load new symbol table from "c:/heob/heob32.exe"? (y or n) y
Reading symbols from c:/heob/heob32.exe...
I will try to debug these, maybe I can figure them out.
Regards
Hannes
next prev parent reply other threads:[~2022-04-03 13:02 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-20 5:58 Joel Brobecker
2022-03-26 15:26 ` Eli Zaretskii
2022-03-26 15:53 ` Joel Brobecker
2022-03-26 16:15 ` Eli Zaretskii
2022-04-07 16:08 ` Tom Tromey
2022-04-07 16:12 ` Eli Zaretskii
2022-04-07 18:00 ` Joel Brobecker
2022-04-07 18:04 ` Simon Marchi
2022-04-07 19:02 ` Tom Tromey
2022-04-07 19:11 ` Joel Brobecker
2022-04-08 13:38 ` Tom Tromey
2022-04-08 14:33 ` Pedro Alves
2022-04-18 15:26 ` Tom Tromey
2022-04-18 16:13 ` Tom Tromey
2022-04-07 18:30 ` Tom Tromey
2022-04-08 6:58 ` Eli Zaretskii
2022-04-18 19:28 ` Tom Tromey
2022-03-26 17:59 ` Eli Zaretskii
2022-03-26 18:34 ` Eli Zaretskii
2022-03-26 18:51 ` Eli Zaretskii
2022-03-27 6:27 ` Eli Zaretskii
2022-03-31 6:23 ` Eli Zaretskii
2022-03-31 9:48 ` Pedro Alves
2022-03-31 11:55 ` Eli Zaretskii
2022-04-01 10:12 ` Andrew Burgess
2022-04-01 11:18 ` Eli Zaretskii
2022-04-01 11:25 ` Eli Zaretskii
2022-04-01 15:21 ` Andrew Burgess
2022-04-01 16:18 ` Eli Zaretskii
2022-04-03 13:02 ` Hannes Domani [this message]
2022-04-03 13:34 ` Eli Zaretskii
2022-04-03 14:03 ` Joel Brobecker
2022-04-03 15:26 ` Hannes Domani
2022-04-03 15:38 ` Eli Zaretskii
2022-04-07 11:09 ` Eli Zaretskii
2022-04-07 18:03 ` Joel Brobecker
2022-04-10 19:06 ` Joel Brobecker
2022-04-11 11:42 ` Eli Zaretskii
2022-04-17 17:28 ` Joel Brobecker
2022-04-19 16:12 ` Andrew Burgess
2022-04-19 16:16 ` Eli Zaretskii
2022-04-20 13:26 ` Andrew Burgess
2022-04-20 17:11 ` Joel Brobecker
2022-04-20 17:30 ` Eli Zaretskii
2022-04-24 15:56 ` Joel Brobecker
2022-04-25 8:48 ` Andrew Burgess
2022-04-07 18:28 ` Tom Tromey
2022-04-07 19:22 ` Pedro Alves
2022-04-08 4:04 ` Eli Zaretskii
2022-04-01 12:36 ` Joel Brobecker
2022-04-01 12:50 ` Eli Zaretskii
2022-04-01 14:12 ` Joel Brobecker
2022-04-01 14:27 ` Eli Zaretskii
2022-04-01 14:31 ` Joel Brobecker
2022-04-08 14:44 ` Pedro Alves
2022-04-08 20:05 ` Eli Zaretskii
2022-03-27 9:55 ` Eli Zaretskii
2022-03-27 1:55 ` Simon Marchi
2022-03-27 5:20 ` Eli Zaretskii
2022-04-07 16:13 ` Tom Tromey
2022-04-07 16:39 ` Eli Zaretskii
2022-03-31 6:21 ` Eli Zaretskii
2022-03-31 9:44 ` Pedro Alves
2022-03-31 11:58 ` Eli Zaretskii
2022-03-31 12:05 ` Pedro Alves
2022-03-31 14:00 ` Eli Zaretskii
2022-04-12 14:01 ` Luis Machado
2022-04-12 17:57 ` Joel Brobecker
2022-04-13 7:36 ` Luis Machado
2022-04-13 12:19 ` Luis Machado
2022-04-13 16:20 ` Jose E. Marchesi
2022-04-17 17:33 ` Joel Brobecker
2022-04-18 1:48 ` Alan Modra
2022-04-26 13:54 ` Luis Machado
2022-04-26 14:56 ` Joel Brobecker
2022-04-26 15:15 ` Luis Machado
2022-04-20 17:33 ` Pedro Alves
2022-04-20 17:52 ` Joel Brobecker
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=1379565857.1750775.1648990951974@mail.yahoo.com \
--to=ssbssa@yahoo.de \
--cc=aburgess@redhat.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/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).