public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@airs.com>
To: mark@codesourcery.com
Cc: gdb@sources.redhat.com, gdb-patches@sources.redhat.com, dj@redhat.com
Subject: Re: PATCH: Do not call xmalloc_failed in expandargv
Date: Tue, 27 Sep 2005 15:17:00 -0000	[thread overview]
Message-ID: <m3mzlya6bt.fsf@gossamer.airs.com> (raw)
In-Reply-To: <200509271451.j8REpKeg029702@sethra.codesourcery.com>

Mark Mitchell <mark@codesourcery.com> writes:

> ! 	    {
> ! 	      fprintf (stderr, "\n%sout of memory\n");
> ! 	      xexit (1);
> ! 	    }

You need an argument to fprintf there, although I don't know just what
it would be.  Or just call fputs.

Either change is approved.

Ian

  reply	other threads:[~2005-09-27 15:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-27 14:51 Mark Mitchell
2005-09-27 15:17 ` Ian Lance Taylor [this message]
2005-09-27 15:22   ` Mark Mitchell
2005-09-27 15:40 ` DJ Delorie
2005-09-27 15:46   ` Mark Mitchell
2005-09-27 18:04     ` DJ Delorie
2005-09-27 18:33       ` Mark Mitchell
2005-09-27 18:35         ` DJ Delorie

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=m3mzlya6bt.fsf@gossamer.airs.com \
    --to=ian@airs.com \
    --cc=dj@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=mark@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).