Complete.Org: Mailing Lists: Archives: freeciv-dev: September 2004:
[Freeciv-Dev] Re: (PR#9901) bug: OSX assert failure on first city being
Home

[Freeciv-Dev] Re: (PR#9901) bug: OSX assert failure on first city being

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: bh@xxxxxxxxxxxxxxxxxxx
Subject: [Freeciv-Dev] Re: (PR#9901) bug: OSX assert failure on first city being created
From: "Jason Short" <jdorje@xxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 1 Sep 2004 14:34:33 -0700
Reply-to: rt@xxxxxxxxxxx

<URL: http://rt.freeciv.org/Ticket/Display.html?id=9901 >

Benoit Hudson wrote:
> <URL: http://rt.freeciv.org/Ticket/Display.html?id=9901 >
> 
> This started about a week or two ago.  When I first create a city (or load a 
> game), this 
> assertion fires:
> improvement.c:289: failed assertion `cont > 0'
> 
> To see this, start a new game, pick any nation, choose a settler, 'b'.  
> Assertion fires 
> immediately.
> 
> The problem is client-side.  When I start separate server and client, the 
> server has a 
> continent number for the tile of the new city, while the client does not 
> (that is, the number is 
> zero).
> 
> I see the problem on OSX but not redhat-7.1 on intel.  Is this a memory 
> corruption issue?

Does this happen with the code from today?  There have been some bugs 
like this but I thought they were all fixed.

And, are you sure you're not building cities on the ocean?  Looks like 
that assertion would go off if you tried.

jason




[Prev in Thread] Current Thread [Next in Thread]