Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>,
	<http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id: <3.0.5.32.19990831114600.00ae5ab0@nema.com>
X-Sender: jmaltz AT nema DOT com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Tue, 31 Aug 1999 11:46:00 -0400
To: Mumit Khan <khan AT xraylith DOT wisc DOT EDU>
From: Jon Maltz <jmaltz AT nema DOT com>
Subject: Re: New snapshots and old binaries 
Cc: cygwin AT sourceware DOT cygnus DOT com
In-Reply-To: <199908311447.JAA16654@mercury.xraylith.wisc.edu>
References: <Your message of "Tue, 31 Aug 1999 10:21:48 EDT."             <3 DOT 0 DOT 5 DOT 32 DOT 19990831102148 DOT 00aec100 AT nema DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

Well, the simple apps compile and run with the aug30th cygwin1.dll
snapshot, and coolview's libcygwin.a.  Slightly less simple apps blow up
with _ctype_ errors (well, a slightly less simple app that happens to
#include <ctype.h>).

So can anyone say what the status of b21 is?  This doesn't seem likely to
get much easier until that is available.

Jon

At 09:47 AM 8/31/99 -0500, Mumit Khan wrote something like this:
>Jon Maltz <jmaltz AT nema DOT com> writes:
>> Sigh...
>> 
>> I installed Cygwin b20.1 from a newly downloaded full.exe on a test box,
>> untar'd Mumit's gcc-2.95, installed coolview, untar'd
>> gcc-2.95-dev-ss.tar.gz, and compiled the simplest c++ app I could think of.
>>  While I was previously entertained by a ton of ctype errors, it now
>> compiles, but won't run.
>> 
>> bash-2.02$ g++ hello.cpp -o test2
>> bash-2.02$ ./test2
>>     0       0 [main] g:\cygnus\usr\home\test2.exe 1073 handle_exceptions:
>> Exception: STATUS_ACCESS_VIOLATION
>>     0   30303 [main] test2 1073 stackdump: Dumping stack trace to
>> test2.exe.stackdump
>> bash-2.02$
>
>There is a good chance that this is due to a bug in the C++ driver, and
>if so, this has been fixed recently (both locally and in GCC CVS tree). 
>For those who follow the gcc patches list, see the recent patches to fix
>memory overrun in the G++ driver and CPP: 
>
>   Linkname: (C++) memory overrun fix for arglist in lang_specific_driver
>   URL: http://egcs.cygnus.com/ml/gcc-patches/1999-08/msg00482.html
>
>and,
>
>   Linkname: Re: (C++) memory overrun fix for arglist in
>   URL: http://egcs.cygnus.com/ml/gcc-patches/1999-08/msg00627.html
>
>Jon, If you'd try out a new driver (g++.exe or c++.exe) to see if it
>fixes the problem, please let me know. 
>
>In the meantime, just use gcc to compile .cc files; the only gotcha is
>that when *linking* C++ code with gcc.exe, you'll have to append -lstdc++
>which c++/g++ does automatically.
>  
>  $ gcc hello.cpp -o test2 -lstdc++
>
>Regards,
>Mumit
>
>

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