Re: Line number of an error

Unfortunately, stack traces will only get you to the method where the error occurred.  A large method could still leave the exception as hard to find.  And I’ve also seen situations where the exception happens inside a different method being called by the one indicated in the stack.  Nil Object Exceptions are extremely difficult as zero information is provided by Xojo as to exactly what object was Nil.

I’ve got one case where I get an NOE and I have been completely unable to find out where it happens.  I can’t duplicate it but I know customers have seen it as I catch it with a try-catch block and email myself where the error came from but I can’t figure what’s causing it.  Almost looks like the framework thinks the actual control placed on the window is Nil!  If Xojo only included more information about such exceptions it would help so much…



> On Aug 25, 2017, at 3:10 AM, Valerio Pittavino <[email protected]> wrote:
> 
> Hi,
> download this
> https://www.dropbox.com/s/leac8whom8iv37m/untitled.xojo_binary_project?dl=0 <https://www.dropbox.com/s/leac8whom8iv37m/untitled.xojo_binary_project?dl=0>
> you can't see the line that has the error but is not complicated to understand the error position using the stack list and the information in class RunTimeException.
> This is useful to send some reports about problem about distribuited softwares
> 
> 
> 2017-08-25 9:40 GMT+02:00 Jean-Luc Arnaud <jean-luc-E/[email protected] <mailto:jean-luc-E/[email protected]>>:
> Thanks for your reply, Valerio.
> 
> Could you please give me more detailed information? Maybe a sample code?
> 
> TIA
> 
> Jean-Luc Arnaud
> 
> 
> 
> Le 24/08/2017 à 22:35, Valerio Pittavino a écrit :
> You should use the stack calls
> 
> Inviato da iPhone
> 
> Il giorno 24 ago 2017, alle ore 16:36, Jean-Luc Arnaud <[email protected] <mailto:jean-luc-E/[email protected]>> ha scritto:
> 
> Hi all,
> 
> Using Exception and, maybe, an Introspection function, is there a way to get the line number of an error?
> 
> MBS functions welcome, too.
> 
> TIA
> 
> -- 
> Jean-Luc Arnaud
> 
> 
> 
> 
> To unsubscribe, email [email protected] <mailto:[email protected]>
> 
> 
> To unsubscribe, email [email protected] <mailto:[email protected]>
> 
> 
> 
> 
> 
> 
> To unsubscribe, email [email protected] <mailto:[email protected]>
> 
> 
> 
> 
> -- 
> Valerio Pittavino
> 
> To unsubscribe, email us here. <mailto:[email protected]>



To unsubscribe, email [email protected]