Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA/doco] add obstacks to gdbint.texi
Date: Tue, 10 Feb 2004 20:11:00 -0000	[thread overview]
Message-ID: <20040210201125.GA21392@nevyn.them.org> (raw)
In-Reply-To: <16425.14578.813770.603105@localhost.redhat.com>

On Tue, Feb 10, 2004 at 03:02:58PM -0500, Elena Zannoni wrote:
> Daniel Jacobowitz writes:
>  > Thanks for doing this!
>  > 
>  > On Tue, Feb 10, 2004 at 12:28:00PM -0500, Elena Zannoni wrote:
>  > > +@value{GDBN} uses various features provided by the libiberty library,
>  > > +for instance the memory management functions xfree and xmalloc, and
>  > > +the obstack extension.
>  > 
>  > Actually, we don't use xfree and xmalloc from libiberty; we use our own
>  > copy in utils.c that behave similarly.
>  > 
> 
> duh, true. libiberty doesn't even have xfree.  So what do we use from
> libiberty? demangler, floatformat, obstack, getopt, what else?

I know I added a use of lbasename.  Oh, and make_relative_prefix.  I
think we use buildargv somewhere but that might just be in the
simulators.  Concat probably has snuck in somewhere.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


      reply	other threads:[~2004-02-10 20:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-10 17:31 Elena Zannoni
2004-02-10 19:04 ` Eli Zaretskii
2004-02-10 19:51   ` Elena Zannoni
2004-02-10 20:06     ` Eli Zaretskii
2004-02-10 20:38       ` Elena Zannoni
2004-02-11  6:09         ` Eli Zaretskii
2004-02-11 15:41           ` Elena Zannoni
2004-02-11 19:27             ` Eli Zaretskii
2004-02-10 19:30 ` Daniel Jacobowitz
2004-02-10 20:06   ` Elena Zannoni
2004-02-10 20:11     ` Daniel Jacobowitz [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=20040210201125.GA21392@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