From: Simon Marchi <simon.marchi@efficios.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] gdb/dwarf: skip broken .debug_macro.dwo
Date: Mon, 12 May 2025 14:08:37 -0400 [thread overview]
Message-ID: <fa1d7153-4020-4c10-a5cc-7d64393061bf@efficios.com> (raw)
In-Reply-To: <87ecwt90id.fsf@tromey.com>
On 5/12/25 1:55 PM, Tom Tromey wrote:
>>>>>> "Simon" == Simon Marchi <simon.marchi@efficios.com> writes:
>
> Simon> + complaint (_("Multiple .debug_macro.dwo sections found in "
> Simon> + "%s, ignoring them."), dwo_file.dbfd->filename);
>
> complaints are only really visible to gdb developers, since most users
> don't (and shouldn't) enable them.
>
> However this is a situation where the issue could cause a user-relevant
> problem (macros not working) and has a fix the user could perhaps enact
> (different compiler). So maybe a warning would be more appropriate?
This would be fine with me. The line would become:
warning (_("Multiple .debug_macro.dwo sections found in "
"%s, ignoring them."), dwo_file.dbfd->filename);
The output looks like this:
(gdb) b main
During symbol reading: Multiple .debug_macro.dwo sections found in /home/smarchi/build/binutils-gdb/gdb/test.dwo, ignoring them.
Breakpoint 1 at 0x11b2: file test.cpp, line 4.
Is the patch ok with that change?
Simon
next prev parent reply other threads:[~2025-05-12 18:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 17:03 [PATCH 1/2] gdb/dwarf: move loops into locate_dw{o,z}_sections Simon Marchi
2025-05-06 17:03 ` [PATCH 2/2] gdb/dwarf: skip broken .debug_macro.dwo Simon Marchi
2025-05-12 17:55 ` Tom Tromey
2025-05-12 18:08 ` Simon Marchi [this message]
2025-05-12 18:48 ` Tom Tromey
2025-05-12 18:50 ` Simon Marchi
2025-05-12 21:06 ` Tom Tromey
2025-05-12 17:52 ` [PATCH 1/2] gdb/dwarf: move loops into locate_dw{o,z}_sections 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=fa1d7153-4020-4c10-a5cc-7d64393061bf@efficios.com \
--to=simon.marchi@efficios.com \
--cc=gdb-patches@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