From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
To: Guinevere Larsen <guinevere@redhat.com>
Cc: gdb-patches@sourceware.org, Guinevere Larsen <blarsen@redhat.com>
Subject: Re: [PATCH v5 1/5] gdb: make gdbarch store a vector of frame unwinders
Date: Wed, 02 Oct 2024 18:49:30 -0300 [thread overview]
Message-ID: <87zfnmb2fp.fsf@linaro.org> (raw)
In-Reply-To: <20241001184235.3710608-2-guinevere@redhat.com> (Guinevere Larsen's message of "Tue, 1 Oct 2024 15:42:31 -0300")
Hello Guinevere,
Just a couple of nits. Regardless:
Reviewed-by: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
Guinevere Larsen <guinevere@redhat.com> writes:
> diff --git a/gdb/frame-unwind.c b/gdb/frame-unwind.c
> index e5f108d3257..b69ae8596a2 100644
> --- a/gdb/frame-unwind.c
> +++ b/gdb/frame-unwind.c
> @@ -31,62 +31,46 @@
> #include "cli/cli-cmds.h"
> #include "inferior.h"
>
> -struct frame_unwind_table_entry
> +/* Default sniffers, that must always be the first in the unwinder list,
> + no matter the architecture. */
> +static constexpr auto standard_unwinders =
> {
> - const struct frame_unwind *unwinder;
> - struct frame_unwind_table_entry *next;
> -};
> + &dummy_frame_unwind,
> + /* The DWARF tailcall sniffer must come before the inline sniffer.
> + Otherwise, we can end up in a situation where a DWARF frame finds
> + tailcall information, but then the inline sniffer claims a frame
> + before the tailcall sniffer, resulting in confusion. This is
> + safe to do always because the tailcall sniffer can only ever be
> + activated if the newer frame was created using the DWARF
> + unwinder, and it also found tailcall information. */
> + &dwarf2_tailcall_frame_unwind,
> + &inline_frame_unwind,
>
Nit: this empty line should be removed.
> -struct frame_unwind_table
> -{
> - struct frame_unwind_table_entry *list = nullptr;
> - /* The head of the OSABI part of the search list. */
> - struct frame_unwind_table_entry **osabi_head = nullptr;
> };
> @@ -355,11 +327,10 @@ maintenance_info_frame_unwinders (const char *args, int from_tty)
> uiout->table_header (25, ui_left, "type", "Type");
> uiout->table_body ();
>
> - for (struct frame_unwind_table_entry *entry = table->list; entry != NULL;
> - entry = entry->next)
> + for (auto unwinder : table)
> {
> - const char *name = entry->unwinder->name;
> - const char *type = frame_type_str (entry->unwinder->type);
> + const char *name = unwinder->name;
> + const char *type = frame_type_str (unwinder->type);
Did you try getting rid of the local vars here, as Simon suggested?
I agree with him that seem unnecessary.
> ui_out_emit_list tuple_emitter (uiout, nullptr);
> uiout->field_string ("name", name);
--
Thiago
next prev parent reply other threads:[~2024-10-02 21:49 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 18:42 [PATCH v5 0/5] Modernize frame unwinders and add disable feature Guinevere Larsen
2024-10-01 18:42 ` [PATCH v5 1/5] gdb: make gdbarch store a vector of frame unwinders Guinevere Larsen
2024-10-02 21:49 ` Thiago Jung Bauermann [this message]
2024-10-08 17:01 ` Guinevere Larsen
2024-10-03 18:33 ` Simon Marchi
2024-10-04 18:37 ` Tom Tromey
2024-10-12 1:34 ` Thiago Jung Bauermann
2024-10-14 18:18 ` Guinevere Larsen
2024-10-17 22:53 ` Tom Tromey
2024-10-18 17:40 ` Guinevere Larsen
2024-10-17 23:41 ` Tom Tromey
2024-10-01 18:42 ` [PATCH v5 2/5] gdb: add "unwinder class" to " Guinevere Larsen
2024-10-02 22:08 ` Thiago Jung Bauermann
2024-10-03 18:46 ` Simon Marchi
2024-10-08 18:22 ` Guinevere Larsen
2024-10-08 18:37 ` Simon Marchi
2024-10-01 18:42 ` [PATCH v5 3/5] gdb: Migrate frame unwinders to use C++ classes Guinevere Larsen
2024-10-03 0:23 ` Thiago Jung Bauermann
2024-10-09 18:16 ` Guinevere Larsen
2024-10-03 20:06 ` Simon Marchi
2024-10-04 5:21 ` Simon Marchi
2024-10-10 14:10 ` Guinevere Larsen
2024-10-10 16:28 ` Simon Marchi
2024-10-09 20:00 ` Guinevere Larsen
2024-10-01 18:42 ` [PATCH v5 4/5] gdb: introduce ability to disable frame unwinders Guinevere Larsen
2024-10-02 6:10 ` Eli Zaretskii
2024-10-04 17:57 ` Guinevere Larsen
2024-10-03 2:45 ` Thiago Jung Bauermann
2024-10-08 19:23 ` Guinevere Larsen
2024-10-06 2:51 ` Simon Marchi
2024-10-09 13:32 ` Guinevere Larsen
2024-10-09 15:38 ` Simon Marchi
2024-10-01 18:42 ` [PATCH v5 5/5] gdb/testsuite: Test for a backtrace through object without debuginfo Guinevere Larsen
2024-10-03 2:47 ` Thiago Jung Bauermann
2024-10-03 6:58 ` Gerlicher, Klaus
2024-10-09 14:56 ` Guinevere Larsen
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=87zfnmb2fp.fsf@linaro.org \
--to=thiago.bauermann@linaro.org \
--cc=blarsen@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=guinevere@redhat.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