Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch rfc] Make GDB's xmalloc match liberties
Date: Sun, 13 Apr 2003 14:12:00 -0000	[thread overview]
Message-ID: <20030413141249.GA20541@nevyn.them.org> (raw)
In-Reply-To: <3E9760F6.1040704@redhat.com>

On Fri, Apr 11, 2003 at 08:42:30PM -0400, Andrew Cagney wrote:
> Per recent discussion, this modifies GDB's xmalloc (actually xmmalloc) 
> so that the behavior matches libiberty's.

Seems reasonable to me, on its own.  However, is it a bug that we were
calling malloc (0) in the first place via NUM_REGS?

I know that call has been discussed before but damned if I can remember
what the discussion said.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-04-13 14:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-12  0:42 Andrew Cagney
2003-04-13 14:12 ` Daniel Jacobowitz [this message]
2003-04-16 14:43 ` Andrew Cagney

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=20030413141249.GA20541@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@redhat.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