From: Christian Biesinger <cbiesinger@google.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PUSHED] gdb/python: Avoid use after free in py-tui.c
Date: Fri, 5 Jun 2020 13:26:36 -0500 [thread overview]
Message-ID: <CAPTJ0XGYggkTxya84ToEhdPJmA5w-_SJFpzbN8nsxdyYXETxyQ@mail.gmail.com> (raw)
In-Reply-To: <20200605182337.981585-1-andrew.burgess@embecosm.com>
On Fri, Jun 5, 2020 at 1:23 PM Andrew Burgess
<andrew.burgess@embecosm.com> wrote:
> - win->window->title = value.get ();
> + win->window->title = value.release ();
Does the old title need to be freed here?
Christian
next prev parent reply other threads:[~2020-06-05 18:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 18:23 Andrew Burgess
2020-06-05 18:26 ` Christian Biesinger [this message]
2020-06-05 18:37 ` Tom Tromey
2020-06-05 20:14 ` Andrew Burgess
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=CAPTJ0XGYggkTxya84ToEhdPJmA5w-_SJFpzbN8nsxdyYXETxyQ@mail.gmail.com \
--to=cbiesinger@google.com \
--cc=andrew.burgess@embecosm.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