Reporting fatal error bugs

[Mark Schonewille]

Hi Dave and everybody who struggles with error handling,

Earlier tonight, I started writing an e-mail to ask you more about  
the error messages you received, but since you have already solved  
the issue, I'll have to re-write my message before I send it.

When Windows reports a fatal error, I suppose there is little to do  
about it, other than to insist that your users/customers try harder  
to find the cause of the problem. If it is Revolution that reports  
the error, you might want to have more options to collect debugging  
information.

Recently, a fellow-developer asked me to write a library to deal with  
execution errors. I have written a library, which I call errorLib,  
that parses the error information and shows this in a dialog window.  
The user can copy the information and paste it into an e-mail, for  
instance. In the IDE, it lets you open and edit a script, just like  
Revolution's built-in error handling features do, but without the  
danger of getting trapped by the revErrorDisplay stack. You can also  
write errors to alog file for further analyses. The library comes  
with detailed documentation.

I would appreciate to receive some feedback. It would be very useful  
to know which features other Revolution developers would like to see.  
Contact me off-list if you would like to test a trial version of my  
ErrorLib.

Best,

Mark

--

Economy-x-Talk
Consultancy and Software Engineering
http://economy-x-talk.com
http://www.salery.biz

Salery is the easiest way to set up your own web store: http:// 
www.salery.biz/salery.html


Op 6-apr-2006, om 18:05 heeft David Beck het volgende geschreven:

>
>
> Hi,
>
>
>
> As I've posted previously to the list many of my users have  
> problems with a
> rev standalone unexpectedly quitting do to illegal operations. I am  
> getting
> more and more reports of this problem (on both Win XP Pro and Home,  
> using a
> standalone built form Rev 2.6.1). There is no specific pattern as  
> to when
> the errors occur that I can determine but for many users it is a daily
> event. In a response to an earlier post somebody suggested that I  
> start a
> bugzilla report for the errors and post any crash logs to that  
> report. Two
> questions:
>
>
>
> 1. Where do I go to log this problem to bugzilla?
>
> 2. How can my users capture the error logs from the Windows illegal
> operation error dialog? I have tried to capture these logs before  
> but have
> not been able to figure it out. I can't copy the contents of the  
> log; I
> can't find an option to save it to a file. The only options are  
> "Send",
> "Don't Send", and view the log, but no way to extract the data!
>
>
>
> Thanks,
>
> Dave