public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Alexandra Petlanova Hajkova <ahajkova@redhat.com>
Cc: Tom Tromey <tom@tromey.com>,  gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix value chain use-after-free
Date: Tue, 14 Feb 2023 15:16:18 -0700	[thread overview]
Message-ID: <877cwjdhal.fsf@tromey.com> (raw)
In-Reply-To: <CAJVr-EOwRS06i_YOP2oDchj046-z4onxyj+4rCRJsx41uk4MKg@mail.gmail.com> (Alexandra Petlanova Hajkova's message of "Tue, 14 Feb 2023 18:05:01 +0100")

Alexandra> I think it's a good solution and I can confirm
Alexandra> gdb.python/py-pp-cast.exp passes for me. But I wasn't able to
Alexandra> apply the patch cleanly, I think it needs to be rebased.

Thank you.  I usually rebase if there are either changes required or
before checking in.  I also push all my patches to my github though it
can be hard sometimes to figure out exactly what branch they're on.

Tom

  reply	other threads:[~2023-02-14 22:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-11  1:08 Tom Tromey
2023-02-14 17:05 ` Alexandra Petlanova Hajkova
2023-02-14 22:16   ` Tom Tromey [this message]
2023-02-27 22:45 ` 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=877cwjdhal.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=ahajkova@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).