From: Tom Tromey <tom@tromey.com>
To: Robert Rossi <bob@brasko.net>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: Optionally print source code to gdb console window
Date: Tue, 07 May 2024 18:52:57 -0600 [thread overview]
Message-ID: <87y18lunti.fsf@tromey.com> (raw)
In-Reply-To: <CA+L9JkgVTv1ZBnb==JKR45dEwghzuGxPMSNXffNbLaeYh4QexQ@mail.gmail.com> (Robert Rossi's message of "Tue, 7 May 2024 17:33:58 -0400")
> The first is that the output looks like this in the suggested case,
> (gdb) n
> 43 in test_main.cpp
Yeah, that's no good.
> 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.
Ok.
> Can you give me some pointers on how the implementation should change?
The new flag shouldn't be in value_print_options. That struct is only
for things affecting value-printing.
Perhaps 'set source open' could be extended to have a new value. Or
perhaps some other 'set source' sub-option could be made. I'm afraid
that normally we bikeshed option names a bit.
> I should also ask, is an option even necessary?
> I think if we remove the source printing from the console when in new-ui mode
> or in mi-mode it would make the most sense. After all, there is a front end displaying
> this information, no?
I personally don't have much stake in it, but it seems to me that if the
Eclipse folks and/or the new-ui implementers already discussed it, then
an option is necessary.
Tom
next prev parent reply other threads:[~2024-05-08 0:53 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 [this message]
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
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=87y18lunti.fsf@tromey.com \
--to=tom@tromey.com \
--cc=bob@brasko.net \
--cc=gdb-patches@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: 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).