comp.lang.idl-pvwave archive: archive » Re: looking for source of a caught runtime error.

Home » Public Forums » archive » Re: looking for source of a caught runtime error.

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: looking for source of a caught runtime error. [message #42951]

Tue, 08 March 2005 09:51

JeremyFaden
Messages: 8
Registered: March 2005

Junior Member

Thanks, "help, /last_message" was exactly what I was looking for!

Report message to a moderator

Re: looking for source of a caught runtime error. [message #42962 is a reply to message #42951]

Mon, 07 March 2005 08:39

Benjamin Hornberger is currently offline

Benjamin Hornberger
Messages: 258
Registered: March 2004

Senior Member

JeremyFaden@gmail.com wrote:
> I'd like to know the location of where a caught
> runtime error occurred. I use "catch, err" to catch any sort
> of runtime error during processing, and then
> throw up a dialog box indicating the error by using !error_state.
> Oddly, !error_state doesn't contain the line number within
> the source code where the error occurred. I feel like I'm missing
> something obvious, but I don't see anything in the documention
> regarding this.
>

Instead of your dialog box, use David's error_message function with the
/traceback keyword set:

http://www.dfanning.com/documents/programs.html#ERROR_MESSAG E

catch, err
IF err NE 0 THEN BEGIN
catch, /cancel
ok = error_message(/traceback, /error)
return
ENDIF

Report message to a moderator

Previous Topic:	xyouts precision
Next Topic:	Re: Error handing in embedded applications

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Fri Oct 10 12:04:48 PDT 2025

Total time taken to generate the page: 1.43979 seconds