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
Message-ID:	<20000914123951.9549.qmail@web114.yahoomail.com>
Date:	Thu, 14 Sep 2000 05:39:51 -0700 (PDT)
From:	Earnie Boyd <earnie_boyd AT yahoo DOT com>
Subject:	Re: STATUS_ACCESS_VIOLATION/segfault problems with cygwin 1.1.4
To:	Albert Graef <Dr DOT Graef AT t-online DOT de>, cygwin AT sources DOT redhat DOT com
MIME-Version:	1.0

--- Albert Graef <Dr DOT Graef AT t-online DOT de> wrote:
> I've been following the threads about STATUS_ACCESS_VIOLATION/segfault
> problems for some days now, since I had really bad troubles running a
> software which works without a hitch under Linux and mingw, and also used to
> work with previous gnuwin32/cygwin releases.
> 

Hmm...  I noticed this problem yesterday from less.  I then check the less
version and installed the 4.0 version I had built --with-ncurses and my
problems went away.

> I've been looking into it, and I am 100% sure that's it a problem with the
> latest cygwin release (maybe with the linker or ar, or with the system
> libraries, you experts know better ;-).
> 

I don't yet know what's causing this either.  When I was installing 1.1.4 over
my existing 1.1.3 I did tar -zxvf /tmp/latest/cygwin/cygwin...gz from the /
directory, then exited all cygwin and replaced the cygwin1.dll with the one
from the tarball and had an unusable system.  No process would start. 
Installing with setup seemed to correct this problem but now I'm having other
side affects.

> The problem occurs whenever you build a static library and a program which
> is linked to both this library and libm.a. I can reproduce it with sources
> as simple as the following:
> 

Adding -lm and -lc to the link process are definite problems.  I haven't
reviewed your sample code yet but rest assured you don't want to `gcc -o foo
foo.c -lc -lm'.  As for using gcc and cygwin1.1.4, I've built the cygwin
runtime several times without these problems while using Cygwin1.1.4 product
itself.

Cheers,

=====
--- <http://earniesystems.safeshopper.com> ---
   Earnie Boyd: <mailto:earnie_boyd AT yahoo DOT com>
            __Cygwin: POSIX on Windows__
Cygwin Newbies: <http://gw32.freeyellow.com/>
           __Minimalist GNU for Windows__
  Mingw32 List: <http://www.egroups.com/group/mingw32/>
    Mingw Home: <http://www.mingw.org/>

__________________________________________________
Do You Yahoo!?
Yahoo! Mail - Free email you can access from anywhere!
http://mail.yahoo.com/

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

- Raw text -