From: Bob Rossi <bob@brasko.net>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Optionally print source code to gdb console window
Date: Tue, 7 May 2024 21:29:19 -0400 [thread overview]
Message-ID: <ZjrVb7OIpttS+fAy@zelda> (raw)
In-Reply-To: <87y18lunti.fsf@tromey.com>
On Tue, May 07, 2024 at 06:52:57PM -0600, Tom Tromey wrote:
> > 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.
That makes sense.
> 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 think it's this behavior of gdb i want to suppress,
https://sourceware.org/gdb/current/onlinedocs/gdb#Source
"When your program stops, GDB spontaneously prints the line where it
stopped"
I'm looking for a way to control printing source lines when printing
frame information? (I'm modifying do_print_frame_info)
Something like 'set frame print_source off' might make sense to me.
Just a thought.
Thanks,
Bob Rossi
next prev parent reply other threads:[~2024-05-08 1:29 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 [this message]
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=ZjrVb7OIpttS+fAy@zelda \
--to=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).