From: Pedro Alves <pedro@palves.net>
To: Robert Rossi <bob@brasko.net>, Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Optionally print source code to gdb console window
Date: Fri, 10 May 2024 20:23:45 +0100 [thread overview]
Message-ID: <f9999cd7-37b5-4a91-a16e-12b6c9e15e82@palves.net> (raw)
In-Reply-To: <CA+L9JkgVTv1ZBnb==JKR45dEwghzuGxPMSNXffNbLaeYh4QexQ@mail.gmail.com>
On 2024-05-07 22:33, Robert Rossi wrote:
> Which is not what the user wants. They don't want to see the updates in the console
> regarding source positions.
> In addition, you can see capabilities they may want, 'list', no longer work.
>
> The reason this issue was noticed in the first place is because this was the
> vision of the original gdb maintainers when using annotate=2. In that mode,
> no source code would be printed to the console. However, in mi new-ui mode
> gdb does print the source code to the console.
>
> My personal opinion is that gdb shouldn't print code to the console in mi mode
> or in new-ui mode. However, there were some people from eclipse a few years
> ago that said they disagreed and that gdb should behave identical in new-ui
> mode and not in new-ui mode, so i've attempted to make an option.
You may be thinking of me. But yes, I disagree, and do think that gdb should
behave identical by default, that was part of the intent/design. I think I
suggested making it an option, so I definitely agree with having one.
prev parent reply other threads:[~2024-05-10 19:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-05 20:57 Robert Rossi
2024-05-06 22:18 ` Robert Rossi
2024-05-07 16:52 ` Tom Tromey
2024-05-07 21:33 ` Robert Rossi
2024-05-08 0:52 ` Tom Tromey
2024-05-08 1:29 ` Bob Rossi
2024-05-08 15:46 ` Tom Tromey
2024-05-08 23:07 ` Bob Rossi
2024-05-09 13:58 ` Tom Tromey
2024-05-10 10:19 ` Andrew Burgess
2024-05-10 18:07 ` Tom Tromey
2024-05-10 19:29 ` Pedro Alves
2024-05-10 19:23 ` Pedro Alves [this message]
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=f9999cd7-37b5-4a91-a16e-12b6c9e15e82@palves.net \
--to=pedro@palves.net \
--cc=bob@brasko.net \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/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).