Xojo Developer Conference
25/27th April 2018 in Denver.
MBS Xojo Conference
6/7th September 2018 in Munich, Germany.

Tracking exception journey up to App.UnhandledException() (Real Studio network user group Mailinglist archive)

Back to the thread list
Previous thread: How to read binary plist files with RB?
Next thread: particle shower?


Reading *CSV Files versus *.Txt Files   -   Claude Stone
  Tracking exception journey up to App.UnhandledException()   -   Eric dLR
   Re: Tracking exception journey up to App.UnhandledException()   -   Charles Yeomans
   Re: Tracking exception journey up to App.UnhandledException()   -   Eric dLR
   Re: Tracking exception journey up to App.UnhandledException()   -   Dennis Birch

Tracking exception journey up to App.UnhandledException()
Date: 29.01.09 17:45 (Thu, 29 Jan 2009 16:45:48 +0000)
From: Eric dLR
Hi,

I need to know where a custom exception was created in the first
place. So I'm using a string property named BirthPlace filled with one
of the constructor parameters. It works fine so far.
But now, I need to track its journey from its birth place to the
App.UnhandledException() event. I thought the Stack array would do the
trick, but it appears that it is holds information only from the last
method without exception handling mechanism. And I need it to be 3 or
4 level deeper. Any suggestion on how to do this?

Eric.

_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>

Re: Tracking exception journey up to App.UnhandledException()
Date: 29.01.09 18:00 (Thu, 29 Jan 2009 12:00:49 -0500)
From: Charles Yeomans

On Jan 29, 2009, at 11:45 AM, Eric dLR wrote:

> Hi,
>
> I need to know where a custom exception was created in the first
> place. So I'm using a string property named BirthPlace filled with
> one of the constructor parameters. It works fine so far.
> But now, I need to track its journey from its birth place to the
> App.UnhandledException() event. I thought the Stack array would do
> the trick, but it appears that it is holds information only from the
> last method without exception handling mechanism. And I need it to
> be 3 or 4 level deeper. Any suggestion on how to do this?
>

Collect that information yourself.

Charles Yeomans

_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>

Re: Tracking exception journey up to App.UnhandledException()
Date: 29.01.09 18:23 (Thu, 29 Jan 2009 17:23:29 +0000)
From: Eric dLR

Le 29 janv. 09 à 17:00, Charles Yeomans a écrit :

> Collect that information yourself.

That's what I tried to do by inserting data in the stack array in each
exception handling block. But they doesn't appear in the stack. I
guess that the stack is built when called or at the first leval
without exception handling mechanism.
So you're right ( again :-) ), I'll do it with my own 'stack' array to
get the Dark Side of an Exception Journey...

Eric.


_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>

Re: Tracking exception journey up to App.UnhandledException()
Date: 29.01.09 18:24 (Thu, 29 Jan 2009 09:24:14 -0800)
From: Dennis Birch
On Thu, Jan 29, 2009 at 9:00 AM, Charles Yeomans <<email address removed>> wrote:
>
> On Jan 29, 2009, at 11:45 AM, Eric dLR wrote:
>
>> Hi,
>>
>> I need to know where a custom exception was created in the first place. So
>> I'm using a string property named BirthPlace filled with one of the
>> constructor parameters. It works fine so far.
>> But now, I need to track its journey from its birth place to the
>> App.UnhandledException() event. I thought the Stack array would do the
>> trick, but it appears that it is holds information only from the last method
>> without exception handling mechanism. And I need it to be 3 or 4 level
>> deeper. Any suggestion on how to do this?
>>
> Collect that information yourself.

Thomas Tempelmann posted an example of doing that on his Web site
which I adapted for my own purposes and have used for several years. I
just looked at his site, and I'm pretty sure this is the source of
that information:

<http://www.tempel.org/rb/exceptionhandling.html>

_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>