On Apr 24, 5:15=A0pm, Vince Hradil <hrad...@[EMAIL PROTECTED]
> wrote:
> On Apr 24, 3:44 pm, David Fanning <n...@[EMAIL PROTECTED]
> wrote:
>
>
>
>
>
> > Folks,
>
> > Has anyone noticed the IDL Workbench ignoring breakpoints?
> > I have this happening to me right this minute on a UNIX
> > machine running IDL 7.0.1. I have a breakpoint in the file
> > at line 172. I confirm this both in the edit window (where
> > the blue dot shows in the channel on the left) and in the
> > Breakpoint view. I save the file. I compile the file. I
> > run the file. It crashes on line 173 after passing through
> > the breakpoint without stopping!
>
> > I've noticed this before, but usually I can get the breakpoint
> > to "take" by unsetting it and setting it again. I've been trying
> > to get this damn file to stop for 10 minutes now. Aaauuughhh!
>
> > Any ideas how I might have gotten into this state?
>
> > Cheers,
>
> > David
>
> > P.S. A "STOP" works. Sigh...
>
> > --
> > David Fanning, Ph.D.
> > Fanning Software Consulting, Inc.
> > Coyote's Guide to IDL Programming (www.dfanning.com)
> > Sepore ma de ni thui. ("Perhaps thou speakest truth.")
>
> Yes - I've noticed this. =A0One time it was because IDL was compiling
> and using a different file (same name) than the one I had open in the
> editor. =A0That darn PATH thing...- Hide quoted text -
>
> - Show quoted text -
I have experienced the identical problem. ITTVIS tech support reported
it as a bug, but said it may be hard to fix.
Here is the test code and comments they sent me. Sometimes the
breakpoints do work and sometimes the code will even ignore a coded
stop.
=46rom ITTVIS:
I was wondering if when you set the breakpoints there is already a
widget running, is that your case?.
We have found the following that could be relevant to your case, let
me know if you can reproduce this example and if this has something to
do with the way you are setting up your breakpoints:
1)Launch the Workbench
2)Create a program with the following contents:
pro test_modal_event,ev
help,ev
print,'set breakpoint after widget is running'
end
pro test_modal
wBase=3Dwidget_base(/row)
wButton=3Dwidget_button(wBase)
widget_control,wBase,/realize
xmanager,'test_modal',wBase ;,/no_block
end
3)Save, compile, and run
4)A widget with a button appears (notice that IDL command line is
greyed out)
5)Click the button
6)Receive a print out stating set breakpoint after widget is running
7)Keep the widget up, but go to the editor and set a breakpoint on the
following line:
print,'set breakpoint after widget is running'
8)Click on the button, and expect IDL to stop at the breakpoint, but
it doesn't
|
