[Freeciv-Dev] Re: civserver freezing? (PR#741)

[Daniel Frazier <dfrazier@xxxxxxxxxxx>]

Here's a link to the save game file that will freeze up within a couple
of turns.  http://alaska.magpage.com/~dfrazier/freeciv/temp.3.gz  In
trying to determine which save it was that would freeze up I got a core
dump and the following error after starting an earlier saved game.

assertion "map_get_tile(map_x, map_y)->worked == NULL" failed: file
"sanitycheck.c", line 144
Abort trap (core dumped)

Here's a link to the core file and the save that generated it...

http://alaska.magpage.com/~dfrazier/freeciv/civserver.core
http://alaska.magpage.com/~dfrazier/freeciv/temp.2.gz

daniel

Thue wrote:
> 
> If you could produce a savegame that consistently froze shortly after it was
> loaded it would be great. Then people could see the bug in actions and it
> should be fairly triviel to fix.
> Note that it might not be possible to produce such a savegame; the bug might
> depend on the server running for an hour :).
> 
> corefiles are always usefull. Send me the one you got please.
> 
> -Thue
> 
> On Wednesday 11 April 2001 20:33, dfrazier@xxxxxxxxxxx wrote:
> > Full_Name: Daniel Frazier
> > Version: 1.11.5-devel
> > Distribution: Built from source
> > Client: Gtk+
> > OS: FreeBSD 4.2-Stable
> > Submission from: (NULL) (216.155.24.136)
> >
> >
> > Using civserver/civclient compiled from cvs sources from Mar-30 I started a
> > new game yesterday and less than an hour into it the game seemed to freeze.
> > There was a core dump, but I don't really know how to debug something using
> > that so I thought I try to compile the latest cvs sources and see how that
> > went.  Everything compiled cleanly but still, less than an hour into a game
> > it would freeze.  This time there was no core dump.  The civserver console
> > was completely unresponsive and all I could do was ctl-c to kill it.  I'm
> > not really sure where to go from here, but I do have the save game file if
> > someone thinks it may be of use.  Is there anything I can do to try to get
> > some information as to what's happening(ie, more verbose debug info)?  If
> > there's any information I could provide to help debug this I'd be happy to
> > do so.  Thanks.