From: Doug Evans <dje@google.com>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Fix double free
Date: Tue, 21 Jul 2009 03:19:00 -0000 [thread overview]
Message-ID: <e394668d0907201833o6b59817ch79a605e603ebed73@mail.gmail.com> (raw)
In-Reply-To: <4A6167BD.7080804@redhat.com>
On Fri, Jul 17, 2009 at 11:12 PM, Keith Seitz<keiths@redhat.com> wrote:
> On 07/17/2009 08:08 PM, Doug Evans wrote:
>>
>> The problem occurs twice in reverse_search_command as well.
>
> Indeed it does! I did not even look!
>
> Updated patch attached.
>
> Keith
>
> ChangeLog
> 2009-07-17 Keith Seitz <keiths@redhat.com>
>
> * source.c (forward_search_command): Don't fclose the stream,
> just run the cleanups.
> (reverse_search_command): Likewise.
>
"works for me".
Thanks, please check in.
[Heh, after this many years it's weird saying that.]
next prev parent reply other threads:[~2009-07-21 1:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-18 0:53 Keith Seitz
2009-07-18 6:12 ` Doug Evans
2009-07-18 18:00 ` Keith Seitz
2009-07-21 3:19 ` Doug Evans [this message]
2009-07-24 3:11 ` Keith Seitz
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=e394668d0907201833o6b59817ch79a605e603ebed73@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@redhat.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