| Re: stop on arithmetic error [message #83571] |
Wed, 20 March 2013 09:55 |
wlandsman
Messages: 743
Registered: June 2000
|
Senior Member |
|
|
On Wednesday, March 20, 2013 12:13:05 PM UTC-4, simona bellavista wrote:
>
> On top of that, I would like to be able to examine the stack (as I would say in fortran), I mean I would like to be able to see where the function was called and with which input values, is this possible?
>
I am a little confused by this part of the question. If you are using the Workbench then you should automatically see the traceback and variables at a breakpoint. If you are at the command line, then HELP should display all the variables; individual variables can be displayed with PRINT, and you can get a traceback with HELP,/TRACE. You can examine variables in the calling program using HELP,LEVEL=-1 --Wayne
|
|
|
|
| Re: stop on arithmetic error [message #83574 is a reply to message #83571] |
Wed, 20 March 2013 09:13  |
simona bellavista
Messages: 56
Registered: December 2009
|
Member |
|
|
of course, I can put !except=0 and put a conditional breakpoint with 'check_math() eq 128' in the offending line, but I wanted to avoid this convolved solution.
On top of that, I would like to be able to examine the stack (as I would say in fortran), I mean I would like to be able to see where the function was called and with which input values, is this possible?
On Wednesday, March 20, 2013 2:12:14 PM UTC+1, simona bellavista wrote:
> I have a code with several arithmetic errors (Floating illegal operand, overflow/undeflow) (sigh!), and I use !EXCEPT=2 for locating them, but idl only tells me the line of the function where there is the error and not where the function is called in the main.
>
>
>
> Is there a way to stop the execution when the error happens? I am using idlwave with IDL 8.2
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
