Darwinbots Forum
Code center => Bugs and fixes => Bug reports => Topic started by: Testlund on September 13, 2014, 01:11:03 PM
-
I've gotten this 3 times the last few days, but haven't managed to catch it in safe mode yet.
Does anyone have time to help me with that?
As I understand it this error can be several different things. It has happened two times in IM and one time offline so far.
Here are the files:
-
Yes, run time errors can happen anywhere in the source, therefor many things can cause them.
It would be cool to have stack tracing like in .NET. Stack tracing will show you the exact line the error happens on and therefor the exact feature of a program that is causing it. Usually that is all the information a programer needs as the error itself is descriptive enough, and smart programers break complex formulas into sections so you can not have say a 'dev/0' and an overflow at the same line.
-
I am seriously looking at winDBG. But I do not know how easy it will be to use as I was not able to install it. Every time it starts installing and figures out I have noon .NET and run on XP it quickly uninstalls everything and happily declares "Setup finished, want to see what is new in latest version?" That is a website redirect btw.
Numsgil, any ideas?
It is looking very low level, but if I can load symbols properly into it and trow a break point on a crash, I would not really care.
-
But with all seriousness: I do really, really want to catch all the remaining bugs at this point and a quick way to do so.
-
I caught this in Safe Mode this morning. :)
-
That is awesome Testlund, I'll fire up windowsXP tomorrow morning, going to save completing my NN bot for later. :)
-
Was not able to recreate it, switching over to hacks.
-
Oh sht, I forgot to disable teleporters during safe mode. You may getting a nasty from one of your other simulations that crashes in the given one. >:( Is it safe to curse in Italian now?
-
Thank you for zipping me that simulation anyway, I found a real ugly loading error in my latest version. :)
-
Found possible cause of an old overflow error. No one bothered to cap the collision vectors. Update soon.
-
Good stuff, I am no longer able to recreate this error for some magical reason.
-
Good one, now the error happens but not all the time.