Better error handling?

Post by **FreeBeer** » Sat Jan 29, 2011 5:58 pm

As many folks know, when Alleg barfs on a file (usually a graphics file) it crashes with an ACCESS_EXCEPTION_VIOLATION. Would it be possible to capture the name of that file and log it before the client dies? This would help enormously in diagnosing some folks' problem with installing the game.

fuzzylunkin1 · Post by **fuzzylunkin1** » Sun Jan 30, 2011 11:42 pm

I believe the built in debugging support will help a lot with this (new to R6). Dump files will be created and someone can look at them if they have the proper symbol file from the exact same build as the client that crashed, meaning they will be able to see the very lines of code that caused the crash.

Post by **FreeBeer** » Mon Jan 31, 2011 1:10 am

That would be a good start, at least. Knowing the line of code would help us positively identify that that it was a problem opening a file (for instance), but it would be really helpful if we could know what that file name is. As you probably know, a single corrupt file can bring down the client and if we could identify the offending file, we'd know which one needs to be replaced.

fuzzylunkin1 · Post by **fuzzylunkin1** » Mon Jan 31, 2011 1:57 am

Well it includes a call stack, which I believe contains that information. Perhaps I'm wrong, though. I forget stuff

.

Post by **pkk** » Mon Jan 31, 2011 5:30 am

fuzzylunkin1 wrote:QUOTE (fuzzylunkin1 @ Jan 31 2011, 12:42 AM) I believe the built in debugging support will help a lot with this (new to R6). Dump files will be created and someone can look at them if they have the proper symbol file from the exact same build as the client that crashed, meaning they will be able to see the very lines of code that caused the crash.

As long it breaks compatibility with ASGS, it's no feature of R6.

Cable · Post by **Cable** » Sat Feb 05, 2011 2:45 pm

We really need better error handling in the Allegsrv code.

It would be very helpfull to kknow why the damn service is barfing and choking.