Describe what you were doing when the crash occurred

Compellor · Post by **Compellor** » Thu Apr 29, 2010 10:37 am

I just experienced a crash in another program, and it occurred to me that if other programs are set up to automatically send information on a crash to the devs, then it might be worthwhile to add that to allegiance. This has probably been brought up before somewhere but I was just curious what the opinion was on adding such a feature.

Andarvi · Post by **Andarvi** » Thu Apr 29, 2010 10:51 am

That is more of a feature of the development enviroment Compellor, not something you 'add' to your own code. Allegiance is C-based? then it should be possibe to link in runtime debugger code, however it's really something you don't want to do so late in the development cycle, as it would cause far more problems that it would ever solve.

madpeople · Post by **madpeople** » Thu Apr 29, 2010 11:17 am

I think this is already on the CSS team's wish list in the form of stack trace from alleg

the.ynik · Post by **the.ynik** » Fri Apr 30, 2010 2:46 pm

Andarvi wrote:QUOTE (Andarvi @ Apr 29 2010, 12:51 PM) That is more of a feature of the development enviroment Compellor, not something you 'add' to your own code. Allegiance is C-based? then it should be possibe to link in runtime debugger code, however it's really something you don't want to do so late in the development cycle, as it would cause far more problems that it would ever solve.

It's actually rather simple to get some rough information where the crash happened.
The crashing application just needs to create a minidump and have some separate (non-crashed) process upload it.
See http://msdn.microsoft.com/en-us/library/ms...28VS.85%29.aspx for details.
VS2010 even has built-in support for debugging dump files. (previously one had to use WinDbg which most devs are unfamiliar with)

However, ASGS is "protecting" allegiance by attaching as debugger. This might affect the ability to handle crashes within Allegiance. ASGS itself could create and upload the dump - it's in the ideal position for this as its already attached as debugger, and is a separate process that can safely upload the data when Allegiance.exe has crashed.
However the alleg devs don't have access to ASGS source code, so I guess we won't see this anytime soon

finnbryant · Post by **finnbryant** » Fri Apr 30, 2010 7:50 pm

EDIT: nevermind. "."

fuzzylunkin1 · Post by **fuzzylunkin1** » Fri Apr 30, 2010 8:01 pm

the.ynik wrote:QUOTE (the.ynik @ Apr 30 2010, 09:46 AM) It's actually rather simple to get some rough information where the crash happened.
The crashing application just needs to create a minidump and have some separate (non-crashed) process upload it.
See http://msdn.microsoft.com/en-us/library/ms...28VS.85%29.aspx for details.
VS2010 even has built-in support for debugging dump files. (previously one had to use WinDbg which most devs are unfamiliar with)

However, ASGS is "protecting" allegiance by attaching as debugger. This might affect the ability to handle crashes within Allegiance. ASGS itself could create and upload the dump - it's in the ideal position for this as its already attached as debugger, and is a separate process that can safely upload the data when Allegiance.exe has crashed.
However the alleg devs don't have access to ASGS source code, so I guess we won't see this anytime soon

Perhaps you should read:

madpeople wrote:QUOTE (madpeople @ Apr 29 2010, 06:17 AM) I think this is already on the CSS team's wish list in the form of stack trace from alleg