would you like this also in the trac?? also - see saved game. is all in the zip file. xD NOTE: this is with the trunk version supplied by buggs... as well as a new exe also supplied by buggs. xD
-------------------
Error occured on Thursday, May 28, 2009 at 22:31:54.
lav_coyote25 wrote:i was hoping you could tell me.
Oh, one of those random crashes that is floating around... Unfortunately, unless I can replicate it, I can't fix it.
One of these days, we will find the issue...
what it was - i reloaded and just started playing the map - cant remember how long it was, possibly 20 to 40 mins... and all i did was build and produce units... same as i always do. the only thing i dont usually do is save a game and then reload it later. that is the only new part. xD
lav_coyote25 wrote:i am wondering if it is part of that savegame routine thingy ( unsure of how)... ??
The whole loading/saving routines are ... O_O
Like I said, we will find the issue one of these days. I am pretty darn sure it is a buffer overrun, or a dangling pointer, but finding where it happens, and when it happens is the most difficult part.
ok here is another - strange part though is the fog of war and the mist of war..... would either of those cause the crash? reason i ask is i normally play mist - this time i played with fog.... it wasnt too long before the crash..perhaps 15 to 20 mins? anyone check those out lately??? xD
here is what is in the rpt file...nothing in the other files.
lav_coyote25 wrote: ok here is another - strange part though is the fog of war and the mist of war..... would either of those cause the crash? reason i ask is i normally play mist - this time i played with fog.... it wasnt too long before the crash..perhaps 15 to 20 mins? anyone check those out lately??? xD
Call stack:
004907F3 C:\Warzone 2100 222trunkrc1\warzone2100.exe:004907F3 world_coord /home/admins/wzTrunk/trunk/src/map.h:243
00491AEA C:\Warzone 2100 222trunkrc1\warzone2100.exe:00491AEA moveUpdateDroid /home/admins/wzTrunk/trunk/src/move.c:3076
004364D0 C:\Warzone 2100 222trunkrc1\warzone2100.exe:004364D0 droidUpdate /home/admins/wzTrunk/trunk/src/droid.c:821
0047C461 C:\Warzone 2100 222trunkrc1\warzone2100.exe:0047C461 gameLoop /home/admins/wzTrunk/trunk/src/loop.c:296
0047E3BC C:\Warzone 2100 222trunkrc1\warzone2100.exe:0047E3BC runGameLoop /home/admins/wzTrunk/trunk/src/main.c:654
Naw, fog of war wouldn't play a role in this...
The main issue is, you see how it goes from main to loop to droid in the call stack? At this point, once it gets out of loop, then we have no idea where the bad values came from. So we need a stack trace that is about 3x bigger (or more), so we can follow through the code between each loop to see what is going on. We can't do that currently with the crash handler.
erm, let me clarify what I meant, having 3 different report files don't really help.
What I need is to go back in time (so to speak), so I can see the 2-3 previous call stacks from the prior loops, so we can find where it is messing up at.
At this time, we don't have the ability to time travel, or have the handler go that far back into the call stack.
So it is just a waiting game, when one day, we will be able to find what is causing this issue.
ok i know you "clarified" but - here is using same map - but different ctd style... if you will... thing is - just immediately prior to it crashing - i saw a vtol land on top of a power generator. yeah i know " strange" so there is something to check on. xD
Error occured on Sunday, May 31, 2009 at 01:21:30.
Program: C:\Warzone 2100 222trunkrc1\warzone2100.exe(warzone2100)
Command line: "C:\Warzone 2100 222trunkrc1\warzone2100.exe" "--fullscreen" "--resolution" "1280x1024" "--cheat"
Version: Version TRUNK r7535 (modified locally) - Built May 24 2009
xD NOTE: this is with the trunk version supplied by buggs... as well as a new exe also supplied by buggs. 
ok here is another