Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Lancelot SIX via Gdb-patches <gdb-patches@sourceware.org>
To: Tom Tromey <tom@tromey.com>
Cc: Lancelot SIX via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH][PR gdb/27133] Avoid use after free with logging and debug redirect
Date: Wed, 27 Jan 2021 22:20:08 +0000	[thread overview]
Message-ID: <YBHnGKC1CzzLDPrD@Plymouth> (raw)
In-Reply-To: <87pn2ke9eb.fsf@tromey.com>

Le Mon, Jan 04, 2021 at 01:26:20PM -0700, Tom Tromey a écrit :
> >>>>> "Lancelot" == Lancelot SIX via Gdb-patches <gdb-patches@sourceware.org> writes:
> 
> Lancelot> My copyright assignment has not yet been signed by FSF, but the change
> Lancelot> should be small enough not to require it. Otherwise, it will need to
> Lancelot> wait a few more days I guess.
> 
> I don't know the state of this -- could you say?
> 
> Lancelot> gdb/ChangeLog:
> 
> Lancelot> 	PR gdb/27133
> Lancelot> 	* cli/cli-interp.c (cli_interp_base::set_logging): Ensure the
> Lancelot> 	unique_ptr is released when the wrapped pointer is kept for later
> Lancelot> 	use.
> 
> Thanks.  Looking at the code I feel like there's probably some cleaner
> way to do this, but this patch is ok regardless.
> 
> Tom

Hi,

I have pushed this commit.

I cannot close the associated bug on bugzilla[1] because my account does
not have enough privileges (I can only comment on tickets). Could someone
close it for me?

Thanks.
Lancelot.


[1] https://sourceware.org/bugzilla/show_bug.cgi?id=27133

      parent reply	other threads:[~2021-01-27 22:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-01 20:11 Lancelot SIX via Gdb-patches
2021-01-04 20:26 ` Tom Tromey
2021-01-04 23:29   ` Lancelot SIX via Gdb-patches
2021-01-27 22:20   ` Lancelot SIX via Gdb-patches [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=YBHnGKC1CzzLDPrD@Plymouth \
    --to=gdb-patches@sourceware.org \
    --cc=lsix@lancelotsix.com \
    --cc=tom@tromey.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