Log in

View Full Version : Crash Testing (Hamsterball 1.5)


Raptisoft
05-31-2004, 09:28 AM
Hi all,

I'm testing a manner of cgi-bin crash test recording in which my program will intercept the GPF in the event of a crash, and dump the resulting info to my server in a text file, so that I can examine it any look for problematic areas.

I'd like to ask for your help! On my server, I've placed a version of Hamsterball that will crash immediately when you reach the goal on one of the levels. (int *x=NULL;*x=0;)

At that time, a window will pop up with some information about your computer (windows version, DX version, etc) and some info for us about where the program crashed at.

You can then hit send report to send the contents of that window to our server, where we can look at it and confirm that it works (if it times out, you might have to click send report a couple times... sometimes it doesn't want to go right through).

Thanks for your help. This won't harm your computer, and it will only send the contents of the window to the server-- no secret info is going across.

This is the "crashing hamsterball installer:"

http://www.raptisoft.com/FYI/SetupHamsterball(CrashTest).exe (5.7mb)

Thanks again!

Raptisoft
05-31-2004, 09:29 AM
Oops! The URL quit at the parenthesis!

Please us this URL instead:

http://www.raptisoft.com/FYI/SetupHamsterballCrashTest.exe

Wayward
05-31-2004, 09:52 AM
Oh dam! I thought "Crashing Hamsterball" was the name of your new game.

Raptisoft
05-31-2004, 09:57 AM
That's the unofficial name of the old one. :)

But Hamsterball 2.0 will have a two player mode with lots of Hamsterball Crashing. :)

Lizardsoft
05-31-2004, 09:58 AM
Neat. Worked very well here (much better than my own attempts at crash detection).

Wayward
05-31-2004, 10:02 AM
Two player? I can't wait for Hamsterball 2.0.

The crash thing worked here. I tried it from windowed mode first because of my firewall, and then tried it fullscreen. It appeared to work fine in both cases.

Raptisoft
05-31-2004, 10:05 AM
Firewall shouldn't be a problem because it's just an http post to a web page. Simple as possible. Maybe I'll try something more complex later, but for the foreseeable future, this should work out.

Basically I wanted to make sure I wasn't running into strange socket problems on other computers. You never know what's going to happen on there, in the wide world.