Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
From:	michael AT weiser DOT saale-net DOT de (Michael Weiser)
To:	"Russell K. Thompson II" <rkthomps AT students DOT uwf DOT edu>
Cc:	cygwin AT sourceware DOT cygnus DOT com
Subject:	Re: Freeciv Binaries
Date:	Fri, 12 Mar 1999 11:59:58 GMT
Message-ID:	<36ecf312.9779642@mail.weiser.saale-net.de>
References:	<36E82137 DOT 95FAF831 AT students DOT uwf DOT edu>
In-Reply-To:	<36E82137.95FAF831@students.uwf.edu>
X-Mailer:	Forte Agent 1.5/32.452
MIME-Version:	1.0
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id KAA30014

Hello Russell, you wrote:
>	I was wondering if anyone has been able to run the freeciv binaries
>available from
>ftp://ftp.franken.de/pub/win32/develop/gnuwin32/cygwin/porters/Weiser_Michael/B20/
>on Windows 95.  My server will run fine but when I run the client I get
>the following message
As I mentioned in the README, civclient tends to crash. I haven't been
able to figure out why, yet. One reason seems to be environment space.
Try to unset all variables not needed to run civclient. At least for
me that solves the problem. Another solution is to *not* use and hence
not set FREECIV_DATADIR and instead run civclient in a directory
containing the datafiles in a dir named 'data'. If that doesn't help
too I'm outof ideas. Perhaps you could try compiling yourself for your
particular system.

For more on this see my post to the list from 98/9/17 20:20:01 GMT
named 'environment space limit in cygwin32?' and it's follow-ups. The
main Problem seems to be a call to XtAppAddTimeOut at line 403 in
xmain.c causing the following XtVaGetValues to SIGSEGV. Unfortunately
I don't have the time and knowledge to research this in detail.

I'll try to find out more anyway.

>BASH.EXE-2.02$ civclient
>1: Using fallback resources - which is OK
This is normal.

>1: Your getpwuid call failed.  Please report this.
This is new to me. Maybe you don't have a valid /etc/passwd?

>[main] C:\CYGNUS\USR\LOCAL\BIN\CIVCLIENT.EXE 1001 (0) handle_exceptions:
>Excepti
>on: STATUS_ACCESS_VIOLATION
>[main] CIVCLIENT 1001 (0) handle_exceptions: Dumping stack trace to
>CIVCLIENT.EX
>E.core
>BASH.EXE-2.02$
This is exactly what I get when running civclient without the above
mentioned precautions.

>	When this happens my X server crashes.
>
>	My X server is X-Win32 from starnet.  If anyone has any ideas please
>let me know.
That shouldn't happen, or at least it doesn't happen for me using the
same Server demo version 4.1 build 6.

Hope I could help.
-- 
bye, Michael

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

- Raw text -