From: "Paul Pluzhnikov" <ppluzhnikov@google.com>
To: "Pedro Alves" <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] [python] Fix for double-free.
Date: Thu, 23 Oct 2008 22:51:00 -0000 [thread overview]
Message-ID: <8ac60eac0810231550k38811cb1wad13b7866a788d46@mail.gmail.com> (raw)
In-Reply-To: <200810232015.36765.pedro@codesourcery.com>
On Thu, Oct 23, 2008 at 12:15 PM, Pedro Alves <pedro@codesourcery.com> wrote:
>> 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.
I *do* already have a test case which shows the bug on the branch.
Committed as above.
Thanks,
--
Paul Pluzhnikov
prev parent reply other threads:[~2008-10-23 22:51 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
2008-10-23 22:51 ` Paul Pluzhnikov [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=8ac60eac0810231550k38811cb1wad13b7866a788d46@mail.gmail.com \
--to=ppluzhnikov@google.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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