surprise Randomhammer crash

Randomhammer crashed—as zerg, no less. It got knocked back to 1 base with a few drones, and started to recover as normal, but after making a couple units... kaboom. Zerg has been recovering reliably from these upsets for a long time now, so it’s a surprise. I’m trying to triangulate the source of the problem from not-quite-adequate information.

The upcoming version 1.4.2 is closing in on being ready. The opponent model changes are finished, except for small details. The remaining work is a little bit of smoothing and a bunch of testing (and probably fixing). In between an untraced crash and a new and fairly complex addition to the opponent model, there’s no guessing how long debugging will take.

Trackbacks

No Trackbacks

Comments

Anon on Wednesday, May 9. 2018:

"trying to triangulate the source of the problem from not-quite-adequate information" is perhaps the reason for the whole EXE vs DLL discussion... :/ By the way, how exactly have you been debugging these things?

Jay Scott on Wednesday, May 9. 2018:

Well, in competition it will be DLL. Less overhead. In this case, the crash log is missing key info, so any rare crash is going to be tedious to pin down. I prefer to find bugs by reading all the functionally related code and noticing them. To alter a saying, if you see deeply enough, all bugs are shallow.

Marian on Thursday, May 10. 2018:

I was able to catch these bugs by running locally + memory logging.
Where memory log would log into a fixed size shared memory.
If you reach the end of the memory frame you will start again on zero (basically cyclic memory log).
Then I could put a simple memory log lines everywhere deep into the implementation and on crash another process would read from the memory.

Add Comment

Name*

Homepage

Comment*

In reply to

E-Mail addresses will not be displayed and will only be used for E-Mail notifications.

To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly.
CAPTCHA