This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [RFC] Suggested ways to remove the need for xm-go32.h

From: Andrew Cagney <cagney at gnu dot org>
To: Eli Zaretskii <eliz at gnu dot org>
Cc: gdb-patches at sources dot redhat dot com
Date: Fri, 24 Sep 2004 10:33:36 -0400
Subject: Re: [RFC] Suggested ways to remove the need for xm-go32.h
References: <01c49d82$Blat.v2.2.2$23875ec0@zahav.net.il> <20040923050534.GA11936@trixie.casa.cgf.cx> <41526D73.nailWK21NVX4@mindspring.com> <20040923080312.GA12351@cygbert.vinschen.de> <01c4a224$Blat.v2.2.2$4d880a20@zahav.net.il>

Date: Thu, 23 Sep 2004 10:03:12 +0200
From: Corinna Vinschen <vinschen@redhat.com>
First I thought that's a good idea, but then again, it requires every
system to support /dev/null.  I'm not sure you'd find a filename which
all systems can agree to.

I agree; I think it will be downright impossible to find such a file
name.  Native configurations could all use /dev/null, but the remote
embedded targets are another story...

The question to ask is ``do all hosts on which GDB will run support this?''. Since this stuff is host dependant, the target (native or remote) doesn't matter.

Andrew

References:
- [RFC] Suggested ways to remove the need for xm-go32.h
  - From: Eli Zaretskii
- Re: [RFC] Suggested ways to remove the need for xm-go32.h
  - From: Christopher Faylor
- Re: [RFC] Suggested ways to remove the need for xm-go32.h
  - From: Michael Chastain
- Re: [RFC] Suggested ways to remove the need for xm-go32.h
  - From: Corinna Vinschen
- Re: [RFC] Suggested ways to remove the need for xm-go32.h
  - From: Eli Zaretskii

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]