This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] [python] Fix for double-free.
- From: Pedro Alves <pedro at codesourcery dot com>
- To: gdb-patches at sourceware dot org
- Cc: Paul Pluzhnikov <ppluzhnikov at google dot com>
- Date: Thu, 23 Oct 2008 20:15:36 +0100
- Subject: Re: [patch] [python] Fix for double-free.
- References: <20081023172158.D13083A6AFD@localhost>
I'll take this one.
On Thursday 23 October 2008 18:21:58, Paul Pluzhnikov wrote:
> Greetings,
>
> I made the change below on archer-tromey-python.
>
Thanks for sending it here.
(((( When I asked before please to send breakage fixes here, I was
refering to breakages that affected everybody's non-python GDB usage, like
the build breakage of the other thread. It's certainly nice to have the
code maintained though, in case people are already trying simple
things out. Thanks again. ))))
> Unfortunately, I can't seem to be able to construct a test case
> which exposes this bug.
>
Weird. Maybe the fact that you can't trigger it in FSF has something
to do with owned_by_gdb not being anywhere? That's strange, because one
would expect to see a double-free then anyway, I guess. Still, with
that in mind, the patch looks correct to me, though.
> OK to commit without a test case?
IMO, yes. I'm sure you'll have testcases that trigger this when
more of the python stuff is in.
> Thanks,
> --
> Paul Pluzhnikov
>
> 2008-10-23 Paul Pluzhnikov <ppluzhnikov@google.com>
>
> * python/python-value (valpy_getitem): Fix heap corruption.
>
--
Pedro Alves