From: Pedro Alves <pedro@palves.net>
To: Tom Tromey <tom@tromey.com>
Cc: gdb@sourceware.org
Subject: Re: GDB BoF notes - GNU Cauldron 2023
Date: Fri, 29 Sep 2023 11:25:15 +0100 [thread overview]
Message-ID: <8777dc8f-3411-7d13-ab9e-46e75f2602d2@palves.net> (raw)
In-Reply-To: <87zg1610zk.fsf@tromey.com>
On 2023-09-28 21:44, Tom Tromey wrote:
> Some other defaults to consider:
>
> set print object on
+1. I've wondered before what was the reason for not making this the default.
Maybe because it requires reading the rtti/vtable, and that can go wrong, and
it was thought that when it fails it's confusing? Dunno. Things may be better
nowadays in the bad scenarios. At least you can do "p -o -- var" nowadays,
but I guess most people don't know about that.
> set breakpoint pending on
+1000. If you get a pending breakpoint due to a typo, you can always delete
the just-created breakpoint...
> set print pretty on
>
> The last one is iffy I guess, maybe people like the compact output. The
> first two I think I've had to tell many people about over the years.
Personally I prefer the compact output most of the times, and only occasionally
do "print -pretty" or "with print pretty".
next prev parent reply other threads:[~2023-09-29 10:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 12:41 Pedro Alves
2023-09-27 13:55 ` Simon Marchi
2023-09-27 14:00 ` Guinevere Larsen
2023-09-29 9:24 ` Lancelot SIX
2023-09-29 9:52 ` Turn history saving on by default? (Re: GDB BoF notes - GNU Cauldron 2023) Pedro Alves
2023-09-29 10:30 ` Guinevere Larsen
2023-09-27 20:27 ` GDB BoF notes - GNU Cauldron 2023 John Baldwin
2023-09-29 9:57 ` Pedro Alves
2023-10-06 21:35 ` John Baldwin
2023-09-28 20:44 ` Tom Tromey
2023-09-29 4:48 ` Sam James
2023-09-29 10:25 ` Pedro Alves [this message]
2023-10-05 7:08 ` Tom de Vries
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=8777dc8f-3411-7d13-ab9e-46e75f2602d2@palves.net \
--to=pedro@palves.net \
--cc=gdb@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).