Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Andreas Schwab <schwab@suse.de>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Kill a warning in linux-low.c
Date: Wed, 06 Feb 2002 07:21:00 -0000	[thread overview]
Message-ID: <20020206102140.A17033@nevyn.them.org> (raw)
In-Reply-To: <jewuxqvlth.fsf@suse.de>

On Wed, Feb 06, 2002 at 01:25:46PM +0100, Andreas Schwab wrote:
> Daniel Jacobowitz <drow@mvista.com> writes:
> 
> |> Waitpid's second argument is an (int *), not a (union wait *).  Committed as
> |> obvious.
> 
> Wouldn't it be better to make w an int instead?

A little digging around in glibc tells me - yes, you're right.  Union
wait is a BSD-ism.

I'll fix this after the other three gdbserver patches get looked at.

--  
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-02-06 15:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-05 14:13 Daniel Jacobowitz
2002-02-06  4:26 ` Andreas Schwab
2002-02-06  7:21   ` Daniel Jacobowitz [this message]
2002-02-20 14:57     ` Daniel Jacobowitz

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=20020206102140.A17033@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=schwab@suse.de \
    /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