Charles Calvert wrote:
I don't know what platform you're deploying on, but on Windows there is
a way of injecting a structured exception handler that will catch the
exceptions at the OS level and tell you whether the problem was in your
code or in a dynamically loaded system or third party library.
Naturally you'll get generic exceptions like "access violation", but
they can still be useful.
I'm using both OS X and Windows.
If this is catching the exceptions at the OS level, how do you feed
that information back into RB? Even writing it to a text file would
be sufficient for me to check on next app launch.
This is for catching bugs in the field as opposed to at my workstation.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
