Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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: Thu, 09 May 2024 07:58:17 -0600	[thread overview]
Message-ID: <878r0j3x52.fsf@tromey.com> (raw)
In-Reply-To: <ZjwFq7YupLD9tSZA@zelda> (Bob Rossi's message of "Wed, 8 May 2024 19:07:23 -0400")

>>>>> "Bob" == Bob Rossi <bob@brasko.net> writes:

Bob> I saw in the NEWS file,
Bob>     show print frame-info
Bob>       This controls what frame information is printed by the commands printing
Bob>       a frame.  This setting will e.g. influence the behaviour of 'backtrace',
Bob>       'frame', 'stepi'.  The python frame filtering also respect this setting.
Bob>       The 'backtrace' '-frame-info' option can override this global setting.

Yeah, sorry.  I was hoping to find some simpler way but I think there
isn't one.

Bob> A new option, but separate from the existing frame-info command, as to
Bob> not impact other areas of gdb.
Bob>   set print frame-info-source-line off
Bob> This is very similar to your approach, however, it lets the user choose
Bob> whatever they want with print frame-info, and then it lets cgdb "subtract" the
Bob> source-line printing from the console in only that case (and not bt case).

Bob> What do you think about this crazyiness?

Works for me.

Tom

  reply	other threads:[~2024-05-09 13:58 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 [this message]
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=878r0j3x52.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