From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Paul Pluzhnikov <ppluzhnikov@google.com>
Subject: Re: [patch] [python] Fix for double-free.
Date: Thu, 23 Oct 2008 19:16:00 -0000 [thread overview]
Message-ID: <200810232015.36765.pedro@codesourcery.com> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2008-10-23 19:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 17:22 Paul Pluzhnikov
2008-10-23 19:16 ` Pedro Alves [this message]
2008-10-23 22:51 ` Paul Pluzhnikov
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=200810232015.36765.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=ppluzhnikov@google.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