From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@palves.net>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/2] info breakpoints improvements
Date: Fri, 20 May 2022 08:57:31 +0300 [thread overview]
Message-ID: <835ym0d9v8.fsf@gnu.org> (raw)
In-Reply-To: <20220519215552.3254012-1-pedro@palves.net> (message from Pedro Alves on Thu, 19 May 2022 22:55:50 +0100)
> From: Pedro Alves <pedro@palves.net>
> Date: Thu, 19 May 2022 22:55:50 +0100
>
> we get:
>
> (top-gdb) info breakpoints
> Num Type Disp Enb Address What
> 1 breakpoint keep y internal_error
> 1.1 y 0x00000000005755a5 in internal_error(char const*, int, char const*, ...) at src/gdb/common/errors.c:54
> 2 breakpoint keep y -qualified internal_error
> 2.1 y 0x00000000005755a5 in internal_error(char const*, int, char const*, ...) at src/gdb/common/errors.c:54
> 3 breakpoint keep y errors.c:54
> 3.1 y 0x00000000005755a5 in internal_error(char const*, int, char const*, ...) at src/gdb/common/errors.c:54
> 3.2 y 0x00007ffff6d50410 in PyErr_SetObject at /usr/src/debug/python2-2.7.15-4.fc27.x86_64/Python/errors.c:54
> 4 breakpoint keep y gdb.c:27
> 4.1 y 0x000055555564107b in main(int, char**) at src/gdb/gdb.c:28
> (top-gdb)
I must confess that the new display is much more cluttered, and
includes redundant information, so it's harder to read. It also makes
the important stuff harder to find. Why exactly is this deemed as
improvement, and in particular, why would we want this behavior as the
default? (I won't mind to have this as opt-in behavior, if someone
finds this useful in some situations.)
> Patch #2 introduces an "info breakpoints -hide-locations" option.
> With that, you get just the breakpoint header rows, showing the
> canonical location spec originally used to set the breakpoint, but not
> what the spec expanded to:
>
> (top-gdb) i b -h
> Num Type Disp Enb What
> 1 breakpoint keep y internal_error
> 2 breakpoint keep y -qualified internal_error
> 3 breakpoint keep y errors.c:54
If we want a concise display that only shows the important parts, I'd
lose the "Disp" column.
Thanks.
next prev parent reply other threads:[~2022-05-20 5:57 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 21:55 Pedro Alves
2022-05-19 21:55 ` [PATCH 1/2] Always show locations for breakpoints & show canonical location spec Pedro Alves
2022-05-20 6:45 ` Eli Zaretskii
2022-05-23 17:04 ` [PATCH v2 " Pedro Alves
2022-05-24 13:06 ` Eli Zaretskii
2022-05-25 19:32 ` Pedro Alves
2022-05-26 12:48 ` Eli Zaretskii
2022-05-26 14:04 ` Pedro Alves
2022-05-26 15:03 ` Eli Zaretskii
2022-05-26 15:10 ` Pedro Alves
2022-05-26 15:33 ` Eli Zaretskii
2022-05-26 19:29 ` Pedro Alves
2022-05-26 19:55 ` Eli Zaretskii
2022-05-26 20:40 ` Pedro Alves
2023-04-10 15:07 ` Andrew Burgess
2022-05-20 7:45 ` [PATCH " Metzger, Markus T
2022-05-23 17:05 ` Lancelot SIX
2022-05-19 21:55 ` [PATCH 2/2] Introduce "info breakpoints -hide-locations" Pedro Alves
2022-05-20 6:48 ` Eli Zaretskii
2022-05-20 5:57 ` Eli Zaretskii [this message]
2022-05-23 17:06 ` [PATCH 0/2] info breakpoints improvements Pedro Alves
2022-05-24 13:14 ` Eli Zaretskii
2022-05-24 13:45 ` Pedro Alves
2022-05-24 8:38 ` Luis Machado
2022-05-24 10:02 ` Pedro Alves
2022-05-24 13:20 ` Eli Zaretskii
2022-05-24 13:29 ` Pedro Alves
2022-05-24 13:43 ` Eli Zaretskii
2022-05-24 13:50 ` Pedro Alves
2022-05-24 14:03 ` Eli Zaretskii
2022-05-24 14:09 ` Pedro Alves
2022-05-24 14:25 ` Eli Zaretskii
2022-05-24 14:33 ` Pedro Alves
2022-05-24 14:11 ` Andreas Schwab
2022-05-24 14:17 ` Pedro Alves
2022-05-24 19:49 ` [PATCH] Show enabled locations with disabled breakpoint parent as "y-" (Re: [PATCH 0/2] info breakpoints improvements) Pedro Alves
2022-05-25 13:57 ` Eli Zaretskii
2022-05-25 19:19 ` Pedro Alves
2022-05-24 14:26 ` [PATCH 0/2] info breakpoints improvements Eli Zaretskii
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=835ym0d9v8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/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).