Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Carl Love via Gdb-patches <gdb-patches@sourceware.org>
To: Guinevere Larsen <blarsen@redhat.com>,
	Simon Marchi <simark@simark.ca>,
	gdb-patches@sourceware.org,
	UlrichWeigand <Ulrich.Weigand@de.ibm.com>,
	pedro@palves.net
Subject: RE: [PATCH 0/2] Fix reverse stepping multiple contiguous PC ranges over the line table.
Date: Tue, 29 Aug 2023 11:55:05 -0700	[thread overview]
Message-ID: <5eb817e36a7879eda7ee6fad0775d21174343fca.camel@us.ibm.com> (raw)
In-Reply-To: <28ab7382-a91a-1ed1-de18-c695ae3669d4@redhat.com>

Guinevere:

On Tue, 2023-08-29 at 14:28 +0200, Guinevere Larsen wrote:
> I have tested this patch with both GCC and Clang. I can verify it
> fixes 
> the issue, adds no regression, and even fixes the final issues when 
> testing gdb.reverse with clang!
> 
> Tested-By: Guinevere Larsen <blarsen@redhat.com>

Thanks for the help testing and that it fixes the clang failures for
test gdb.reverse.

                   Carl 


  reply	other threads:[~2023-08-29 18:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25 15:50 Carl Love via Gdb-patches
2023-08-25 15:53 ` [PATCH 1/2] Add gdb_compile options column-info and no-column-info Carl Love via Gdb-patches
2023-08-25 15:57 ` [PATCH 2/2 ver 8] Fix reverse stepping multiple contiguous PC ranges over the line table Carl Love via Gdb-patches
2023-08-29 12:28 ` [PATCH 0/2] " Guinevere Larsen via Gdb-patches
2023-08-29 18:55   ` Carl Love via Gdb-patches [this message]
2023-09-05 15:12     ` Carl Love via Gdb-patches
2023-09-25 22:15       ` Carl Love via Gdb-patches
2023-11-02 17:30         ` PING " Carl Love
  -- strict thread matches above, loose matches on Subject: below --
2023-08-07 18:54 Carl Love via Gdb-patches

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=5eb817e36a7879eda7ee6fad0775d21174343fca.camel@us.ibm.com \
    --to=gdb-patches@sourceware.org \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=blarsen@redhat.com \
    --cc=cel@us.ibm.com \
    --cc=pedro@palves.net \
    --cc=simark@simark.ca \
    /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