Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/2] Cleanup in Python frame_object
Date: Wed, 08 Jul 2026 13:51:05 +0100	[thread overview]
Message-ID: <87jyr5fxvq.fsf@redhat.com> (raw)
In-Reply-To: <cover.1780393815.git.aburgess@redhat.com>

Andrew Burgess <aburgess@redhat.com> writes:

> While working on another patch I ran into an issue with Python's frame
> handling, this got me looking at how Python holds a frame's id.
>
> GDB's frame-id handling has evolved since the Python frame related
> code was added, and I think we can now clean up the Python code, and
> fix a small bug in the process.
>
> Patch #1 is a small testsuite cleanup.
>
> Patch #2 is the actual change to the Python code, updates to the
> expected output for a couple of tests, and a new test that exposes the
> bug.
>

I've gone ahead and checked this in.  Let me know if any issues show
up.

Thanks,
Andrew


      parent reply	other threads:[~2026-07-08 12:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-02  9:54 Andrew Burgess
2026-06-02  9:54 ` [PATCH 1/2] gdb/testsuite: don't overwrite test executable in py-frame.exp Andrew Burgess
2026-06-02  9:54 ` [PATCH 2/2] gdb/python: remove frame_object::frame_id_is_next as unnecessary Andrew Burgess
2026-07-08 12:51 ` Andrew Burgess [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=87jyr5fxvq.fsf@redhat.com \
    --to=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