Lucky_Jack Lucky_Jack

Crash, but no diagnostics.

▼

Crash, but no diagnostics.

from Stardock Forums
I had a crash that I can not explain. There is nothing that I can ponit a finger at that could give
any clue as to the cause. I don't know how to force this blankety-blank Windows ME to provide registers
when a crash occurs. There was nothing in the debug file that gives any hit, or any anomaly, but I did
save it and can send it to someone at stardock if you will give me a name and address.

Is it possible to have the GalCiv exec trap program checks or other sudden terminations and put useful
information, such as registers, into the debug file? I would really like to be able to tell you more than
"I got a crash".

Cheers,
Jack
445 views 27 replies
Reply #26 from Stardock Forums Top
Just for the fun of it, and to see how well "smartexception" works, I swapped some improvements back to tech 63 and
tried again. I found that the number 13 is significant, that is, it can handle 13 improvements for one tech. Perhaps,
if this is the correct limit, it would be a good idea to add a comment at the top of the improvement file to reflect
this.

Also, I am going to post the exception report in the thread introducing "smartexception" so that all can see how great
this tool is for debugging. Guess what! GalCiv.exe was getting a trap 5 from a routine called "call stack".

Cheers,
Jack
Reply #27 from Stardock Forums Top
Well, the place that it's crashing is where it's trying to make a list of all the improvements that are now available upon the reasearch completing. So, basically, when it gets beyond 500 characters (including newline characters), it crashes because it goes out of bounds of the string. It's not supposed to have 13+ techs; the person who entered it that way evidently got bored or something. Eventually, someone is going to have to go through and put accurate descriptions of the techs and accurate required tech values in.
Elemental: Reforged