From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: Avoid obstack_free in cp-namespace.c
Date: Mon, 09 Feb 2004 22:25:00 -0000 [thread overview]
Message-ID: <20040209222532.GA3931@nevyn.them.org> (raw)
In-Reply-To: <yf2wu6wc5u7.fsf@hawaii.kealia.com>
On Mon, Feb 09, 2004 at 01:15:28PM -0800, David Carlton wrote:
> On Mon, 9 Feb 2004 16:10:10 -0500, Daniel Jacobowitz <drow@mvista.com> said:
>
> > What do you think of this change? It makes the assumption that
> > lookup_block_symbol will not allocate anything on the objfile
> > obstack, which is no longer true in a patch I'm testing. I really
> > dislike obstack_free for this exact reason.
>
> Makes sense to me.
Checked in.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-02-09 22:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-09 21:10 Daniel Jacobowitz
2004-02-09 21:20 ` David Carlton
2004-02-09 22:25 ` Daniel Jacobowitz [this message]
2004-02-09 22:42 ` Elena Zannoni
2004-02-10 5:44 ` Eli Zaretskii
2004-02-10 17:28 ` Elena Zannoni
2004-02-10 18:55 ` Eli Zaretskii
2004-02-10 5:44 ` Eli Zaretskii
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=20040209222532.GA3931@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.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