From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simon.marchi@efficios.com>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] gdb/dwarf: skip broken .debug_macro.dwo
Date: Mon, 12 May 2025 15:06:44 -0600 [thread overview]
Message-ID: <87o6vx7d3v.fsf@tromey.com> (raw)
In-Reply-To: <1b5cc206-47b6-4745-b3fd-fec87f6389ef@efficios.com> (Simon Marchi's message of "Mon, 12 May 2025 14:50:12 -0400")
>>>>> "Simon" == Simon Marchi <simon.marchi@efficios.com> writes:
>> Yeah, it's fine by me either way -- I was really asking for your opinion
>> though, not requesting a change.
Simon> I don't really know the rule of thumb here, so I trust you. Warning
Simon> seems fine to me.
I hold the somewhat extreme view that complaints are useless and we
should remove them. But anyway they are normally used to report
pedantic DWARF bugs that aren't user-actionable.
Tom
next prev parent reply other threads:[~2025-05-12 21:10 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
2025-05-12 18:48 ` Tom Tromey
2025-05-12 18:50 ` Simon Marchi
2025-05-12 21:06 ` Tom Tromey [this message]
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=87o6vx7d3v.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.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