From: Daniel Jacobowitz <drow@mvista.com>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: protect breakpoint commands from being freed
Date: Wed, 17 Dec 2003 18:32:00 -0000 [thread overview]
Message-ID: <20031217183208.GA29882@nevyn.them.org> (raw)
In-Reply-To: <vt2isklntuw.fsf@zenia.home>
On Sat, Dec 13, 2003 at 12:56:39AM -0500, Jim Blandy wrote:
>
> 2003-12-02 Jim Blandy <jimb@redhat.com>
>
> * breakpoint.c (bpstat_do_actions): To ensure that
> clear_proceed_status doesn't free the command tree we're
> evaluating out from under us, zero the bpstat's pointer to it, and
> take care of freeing it ourselves.
> * cli/cli-script.c (make_cleanup_free_command_lines): Make this
> function externally visible.
> * cli/cli-script.h (make_cleanup_free_command_lines): New
> declaration.
I don't believe anyone has objected to this patch, and it looks good to
me. Please check this in.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-12-17 18:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-13 5:59 Jim Blandy
2003-12-13 18:56 ` Andrew Cagney
2003-12-13 20:13 ` Jim Blandy
2003-12-13 22:42 ` Jim Blandy
2003-12-17 18:32 ` Daniel Jacobowitz [this message]
2003-12-22 3:43 ` Jim Blandy
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=20031217183208.GA29882@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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