Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@is.elta.co.il>
To: Keith Seitz <keiths@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] defs.h _WIN32 defined by Win98, too
Date: Wed, 01 Aug 2001 01:49:00 -0000	[thread overview]
Message-ID: <Pine.SUN.3.91.1010801114944.14932J-100000@is> (raw)
In-Reply-To: <Pine.GSO.4.33.0107311445130.28966-100000@makita.cygnus.com>

On Tue, 31 Jul 2001, Keith Seitz wrote:

> As a result of this change:
> 
> 2001-06-13  Eli Zaretskii  <eliz@is.elta.co.il>
> 
>         * config/i386/xm-go32.h (SLASH_P, ROOTED_P, SLASH_CHAR)
>         (SLASH_STRING): Remove unised definitions.
>         * config/i386/xm-cygwin.h: Likewise.
> 
> Win98 no longer works under cygwin:
> 
> (gdb) file gdb.exe
> Loading symbols from gdb.exe...done
> (gdb) run
> `/home/keiths/sources/insight/gdb\gdb.exe' has disappeared; keeping its
> symbols.
> 
> Starting program: /home/keiths/sources/insight/gdb\gdb.exe
> Error creating process /home/keiths/sources/insight/gdb\gdb.exe (error 2)
> [often crashes here]
> 
> Apparently, Win98 defines _WIN32 somewhere...

So perhaps there's a bug in Cygwin ;-)

Anyway, didn't Chris say that _WIN32 should be removed from GDB
everywhere?  If that's so, the ifdef _WIN32 should be simply deleted,
instead of lumping more ifdefs on top of it.  For SLASH_STRING in
particular, this shouldn't be a problem at all, since Windows supports
forward slashes as well as backslashes, even if GDB is built with MS 
run-time DLLs.


       reply	other threads:[~2001-08-01  1:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.GSO.4.33.0107311445130.28966-100000@makita.cygnus.com>
2001-08-01  1:49 ` Eli Zaretskii [this message]
2001-08-01  7:48   ` Keith Seitz
2001-08-01  8:23     ` Eli Zaretskii
2001-08-01  8:32       ` Keith Seitz
2001-08-01  8:39         ` Eli Zaretskii
2001-08-02 13:40           ` Christopher Faylor
2001-08-02 13:57             ` Keith Seitz
2001-08-02 14:11               ` Andrew Cagney
2001-08-02 14:37                 ` Keith Seitz

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=Pine.SUN.3.91.1010801114944.14932J-100000@is \
    --to=eliz@is.elta.co.il \
    --cc=gdb-patches@sources.redhat.com \
    --cc=keiths@cygnus.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