Warzone2100 Version
SVN - revision 1328
Operating System
Gentoo Linux x86_64
Hardware Information
AMD64 2800+
ATI Radeon 9600 (RV350AQ)
SB Audigy LS
Asus K8N motherboard
Warzone2100 Configuration
http://rafb.net/p/O28AsP27.html
Bug Description
This one was a random segfault, meaning it is not reproducible, because I didn't save it before.
It was way into a skirmish against the computer (meaning >1.5 hours of playing, huge map, very advanced research), just before i went for the final assault.
This is the output on my console:
http://rafb.net/p/tA7c7I54.html
This is the core dump:
http://rafb.net/p/jwKb9W71.html
segfault in long skirmish
- Watermelon
- Code contributor
- Posts: 551
- Joined: 08 Oct 2006, 09:37
Re: segfault in long skirmish
According to the console output,it's a missing file problem.(a filename case problem I guess)
Could you please try using '--debug all' commandline option when launching warzone next time you play it?because it might give us an idea of the name of the missing file(s).
note:using '--debug all' will generate a relatively big stderr whose size is up to few hundreds MBs after a prelonged game.
Could you please try using '--debug all' commandline option when launching warzone next time you play it?because it might give us an idea of the name of the missing file(s).
note:using '--debug all' will generate a relatively big stderr whose size is up to few hundreds MBs after a prelonged game.
tasks postponed until the trunk is relatively stable again.