Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner via Gdb-patches <gdb-patches@sourceware.org>
To: Kevin Buettner via Gdb-patches <gdb-patches@sourceware.org>
Cc: Kevin Buettner <kevinb@redhat.com>,
	Guinevere Larsen <blarsen@redhat.com>
Subject: Re: [PATCH v3 1/2] gdb/record: print frame information when exiting a recursive call
Date: Wed, 27 Sep 2023 16:22:31 -0700	[thread overview]
Message-ID: <20230927162231.5d301671@f37-zws-nv> (raw)
In-Reply-To: <20230927142619.04ca311d@f37-zws-nv>

On Wed, 27 Sep 2023 14:26:19 -0700
Kevin Buettner wrote:

> (I'll continue to study it here - there may be something weird going
> on with the VM upon which I'm testing...)

Using a number of Fedora releases (and VMs), I tested
gdb.dwarf2/dw2-out-of-range-end-of-seq.exp with GDB builds with Gwen's
patch applied...

F35: pass
F36: pass
F37: pass
F38: fail
F38 (updated): fail
F38 (updated, no -O2 in GDB part of build): fail
F38 (circa May, 2023): fail
F38 (aarch64): pass
F39: pass
F40 (aka rawhide): pass

I used two different x86_64 F38 VMs, but they're related.  The "circa
May" F38 VM was cloned from the main one that I use for much of my
work, but I cloned it to look at a specific problem and
(intentionally) had not updated it since cloning.

I've also removed the debuginfod cache. Even with it deleted, I'm
still seeing the same failure on the x86_64 Fedora 38 VMs.

For all machines which show a pass for dw2-out-of-range-end-of-seq.exp,
I ran the new test using TESTS=gdb.reverse/recursion.exp to make sure
that I was really testing against a build with Gwen's patch applied. 
In each case, I saw 8 PASSes, so I was indeed testing what I had
thought I was.

I'll now do some actual debugging, comparing what happens with and
without Gwen's patch...

Kevin


  reply	other threads:[~2023-09-27 23:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-27 10:19 [PATCH v3 0/2] Improving frame printing with recursive Guinevere Larsen via Gdb-patches
2023-09-27 10:19 ` [PATCH v3 1/2] gdb/record: print frame information when exiting a recursive call Guinevere Larsen via Gdb-patches
2023-09-27 21:26   ` Kevin Buettner via Gdb-patches
2023-09-27 23:22     ` Kevin Buettner via Gdb-patches [this message]
2023-09-28  1:57       ` Kevin Buettner via Gdb-patches
2023-10-02 13:11         ` Guinevere Larsen via Gdb-patches
2023-09-27 10:19 ` [PATCH v3 2/2] gdb/infrun: simplify process_event_stop_test Guinevere Larsen 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=20230927162231.5d301671@f37-zws-nv \
    --to=gdb-patches@sourceware.org \
    --cc=blarsen@redhat.com \
    --cc=kevinb@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