[Gambas-user] Searching an error in the whole class

[Benoit Minisini]

On mercredi 14 mai 2008, Rolf-Werner Eilert wrote:
> Benoit Minisini schrieb:
> > On mercredi 14 mai 2008, Rolf-Werner Eilert wrote:
> >> Hi,
> >>
> >> Is it possible to let the program jump to an error routine if an error
> >> occurs SOMEWHERE in the class?
> >>
> >> I cannot find the reason for an error in one of my apps the students
> >> use. This error occurs especially when lots of french letters and/or
> >> apostrophies are written, but it is not predictable. So I cannot try it
> >> for myself (what I did, but it didn't run into an error...)
> >>
> >> Of course, they use a compiled version of the program. So I have to log
> >> the error into a file and search for the reason. But with TRY etc. I can
> >> only catch an error within one specific function... Since I don't know
> >> where the error occurs, it would be nice to let the program jump into
> >> some "global" error routine.
> >>
> >> Thanks for your hints!
> >>
> >> Rolf
> >
> > Why can't you know where the error occurs? When you compile the program,
> > check the check-box that tell the compiler to keep debuggin information
> > inside the executable, and you will get the location of the error. You
> > can even get the backtrace on the standard error output!
> >
> > Regards,
>
> You mean an error message like this?
>
> ######
> This application has raised an unexpected error and must abort.
>
> [-1] Tab is not empty.
>
> Form 1.?.0
> ######
>
> What does this tell me, and how should I locate an error with this
> information? (This is an example from another program where I know how
> to produce a runtime error...)
>
> Regards
>
> Rolf
>

You get this message when you make your executable without the debugging 
information (so the interpreter can only print the class where the problem 
occurs, Form1). 

With debugging information, you should have a function name instead of "?", 
and a line number instead of "0".

-- 
Benoit Minisini