Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Andrew Burgess <aburgess@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCHv3] gdb: resolve class name via DW_AT_signature in cooked index
Date: Thu, 10 Sep 2026 12:18:49 -0400	[thread overview]
Message-ID: <942dfd6e-60d5-4443-bbbc-7d2f67d2ba05@simark.ca> (raw)
In-Reply-To: <897f5eb957bdfd90cd3fd5efa662021ed5c2aef2.1788269262.git.aburgess@redhat.com>



On 2026-09-01 09:31, Andrew Burgess wrote:
> In v3:
> 
>   - I forgot to run check-all-boards on v2.  There were some failures
>     due to GDB's output not matching the patterns, I've fixed what I
>     could in this iteration.
> 
>   - While looking at the different patterns I reworded one of the
>     complaint messages in cooked-index-shard.c to match a warning that
>     is emitted from elsewhere in the DWARF reader.  There's no real
>     functional change, it's just the wording that's updated.
> 
>   - There are still some check-all-boards failures, but I believe
>     these are all wider issues when running DWARF assembler tests
>     using the check-all-boards rule, so I'm ignoring them for now.
> 
> In v2:
> 
>   - Complete rewrite to address the issues that Tom raised.
> 
>   - Rebase to HEAD and retest.
> 
>   - New tests added to cover the DWO case and an error case.
> 
> Thanks,
> Andrew
> 
> ---

I just wanted to point out that your use of --- is the opposite of the
convention, normally the "real" commit message goes above and the
temporary message goes below.  When applying this email as a whole
(either with git-am or b4), it keeps the wrong part as the commit
message.  I would suggest either using the reversed order, or using a
different marker if you prefer to keep the temporary message on top.

Simon

      parent reply	other threads:[~2026-09-10 16:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-19 10:03 [PATCH] [GDB 18] " Andrew Burgess
2026-08-21 17:07 ` Tom Tromey
2026-08-28 21:30 ` [PATCHv2] " Andrew Burgess
2026-09-01 13:31   ` [PATCHv3] " Andrew Burgess
2026-09-10 16:11     ` Simon Marchi
2026-09-11 19:18       ` Tom Tromey
2026-09-12  2:06         ` Simon Marchi
2026-09-14 13:23           ` Andrew Burgess
2026-09-14 14:57             ` Simon Marchi
2026-09-14 15:38               ` Tom Tromey
2026-09-15 10:25               ` Andrew Burgess
2026-09-15 15:01                 ` Tom Tromey
2026-09-15 15:55                   ` Simon Marchi
2026-09-15 17:21                     ` Simon Marchi
2026-09-14 15:36             ` Tom Tromey
2026-09-10 16:18     ` Simon Marchi [this message]

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=942dfd6e-60d5-4443-bbbc-7d2f67d2ba05@simark.ca \
    --to=simark@simark.ca \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    /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