From: Tom Tromey <tom@tromey.com>
To: Bob 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: Wed, 08 May 2024 09:46:16 -0600 [thread overview]
Message-ID: <87a5l05mt3.fsf@tromey.com> (raw)
In-Reply-To: <ZjrVb7OIpttS+fAy@zelda> (Bob Rossi's message of "Tue, 7 May 2024 21:29:19 -0400")
>>>>> "Bob" == Bob Rossi <bob@brasko.net> writes:
>> 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.
Bob> I think it's this behavior of gdb i want to suppress,
Bob> https://sourceware.org/gdb/current/onlinedocs/gdb#Source
Bob> "When your program stops, GDB spontaneously prints the line where it
Bob> stopped"
Bob> I'm looking for a way to control printing source lines when printing
Bob> frame information? (I'm modifying do_print_frame_info)
Bob> Something like 'set frame print_source off' might make sense to me.
Bob> Just a thought.
How about adding a new value to "set print frame-info"?
Like "set print frame-info nothing"?
Tom
next prev parent reply other threads:[~2024-05-08 15:46 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 [this message]
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=87a5l05mt3.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).