Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Wed, 22 Nov 2000 16:19:42 -0500
From: Phil Edwards <pedwards AT disaster DOT jaj DOT com>
To: Zack Weinberg <zackw AT Stanford DOT EDU>
Cc: Kelley Cook <Kelley DOT Cook AT home DOT com>,
        "GCC-Bugs AT gcc DOT gnu DOT org" <GCC-Bugs AT gcc DOT gnu DOT org>,
        "GCC-patches AT gcc DOT gnu DOT org" <GCC-patches AT gcc DOT gnu DOT org>,
        Cygwin mailing list <Cygwin AT sources DOT redhat DOT com>
Subject: Re: Reason for cygwin GCC 2.97 non-bootstrap found
Message-ID: <20001122161942.A20971@disaster.jaj.com>
Mail-Followup-To: Zack Weinberg <zackw AT Stanford DOT EDU>,
	Kelley Cook <Kelley DOT Cook AT home DOT com>,
	"GCC-Bugs AT gcc DOT gnu DOT org" <GCC-Bugs AT gcc DOT gnu DOT org>,
	"GCC-patches AT gcc DOT gnu DOT org" <GCC-patches AT gcc DOT gnu DOT org>,
	Cygwin mailing list <Cygwin AT sources DOT redhat DOT com>
References: <200011211839 DOT eALIdOd15553 AT ahmlir2 DOT mail DOT eds DOT com> <20001121162522 DOT G17712 AT wolery DOT stanford DOT edu> <20001121195005 DOT A17637 AT disaster DOT jaj DOT com> <20001121171653 DOT I17712 AT wolery DOT stanford DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20001121171653.I17712@wolery.stanford.edu>; from zackw@Stanford.EDU on Tue, Nov 21, 2000 at 05:16:53PM -0800

On Tue, Nov 21, 2000 at 05:16:53PM -0800, Zack Weinberg wrote:
> 
> Uh oh, that means I don't understand what's going on.  Can you try
> this augmented version of the test program, which probes things a bit
> more thoroughly?  Now I want the output and the exit status.  [If you
> know how, also try to turn on Cygwin's internal debug logging and tell
> me what that reports.]

I don't know how, but if you still need to see the internal logging,
just let me know how.

The new'n'improved test shows:

    3% gcc zw.c
    4% ./a.exe
    mmap: error 0
    munmap: Invalid argument
    signal: error 0
    5% echo $?
    1
    6%

-- 
pedwards at disaster dot jaj dot com  |  pme at sources dot redhat dot com
devphil at several other less interesting addresses in various dot domains
The gods do not protect fools.  Fools are protected by more capable fools.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com