Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: gdb-patches@sourceware.org
Subject: [RFA 0/3] Better control about frame information to print.
Date: Sat, 04 May 2019 21:57:00 -0000	[thread overview]
Message-ID: <20190504215538.29821-1-philippe.waroquiers@skynet.be> (raw)

When printing big stacktraces having a lot of functions with a lot of
arguments, it can be handy to see a lot less information in the
printed frames.

With the new settings, it is possible to have backtraces such as:
  (gdb) bt
  #0  break_me ()
  #1  call_me (...)
  #2  main ()
  (gdb)

that are only showing the level, the function name and the presence of
arguments.



             reply	other threads:[~2019-05-04 21:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-04 21:57 Philippe Waroquiers [this message]
2019-05-04 21:57 ` [RFA 2/3] Test 'set print frame-info|frame-arguments presence' Philippe Waroquiers
2019-05-04 21:57 ` [RFA 3/3] Document " Philippe Waroquiers
2019-05-05 16:43   ` Eli Zaretskii
2019-05-04 21:57 ` [RFA 1/3] Implement " Philippe Waroquiers
2019-05-05 20:24   ` Andreas Schwab
2019-05-06 19:43   ` Tom Tromey

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=20190504215538.29821-1-philippe.waroquiers@skynet.be \
    --to=philippe.waroquiers@skynet.be \
    --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