| Re: IDL Workbench Ignoring Breakpoints [message #60060] |
Thu, 24 April 2008 15:34 |
peter.n.kupferman
Messages: 2
Registered: April 2008
|
Junior Member |
|
|
On Apr 24, 6:16 pm, David Fanning <n...@dfanning.com> wrote:
> peter.n.kupfer...@aero.org writes:
>> 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.
>
> I guess I could understand if a widget program was involved.
> At least I can imagine the Workbench being confused about
> what event loop it was in. But I have one file open in the
> Workbench and I am running code that should result in a
> plot. I wish to stop after I open the window for the plot,
> but before I actually draw the plot. (I'm trying to examine
> the data to see why it is being plotted incorrectly.)
>
> It really is a pretty simple set-up. No widgets, nothing else
> going on. Weird.
>
> Cheers,
>
> David
>
> --
> 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.")
David,
Unfortunately, your situation is the same as mine. In fact, if you set
the no_block keyword in their
test code, the breakpoint does work, and I almost always set it in my
programs. At least they are aware
of some issues related to setting breakpoints, but I can't find a
repeatable pattern when I have problems.
|
|
|
|
| Re: IDL Workbench Ignoring Breakpoints [message #60061 is a reply to message #60060] |
Thu, 24 April 2008 15:16  |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
peter.n.kupferman@aero.org writes:
> 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.
I guess I could understand if a widget program was involved.
At least I can imagine the Workbench being confused about
what event loop it was in. But I have one file open in the
Workbench and I am running code that should result in a
plot. I wish to stop after I open the window for the plot,
but before I actually draw the plot. (I'm trying to examine
the data to see why it is being plotted incorrectly.)
It really is a pretty simple set-up. No widgets, nothing else
going on. Weird.
Cheers,
David
--
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.")
|
|
|
|
| Re: IDL Workbench Ignoring Breakpoints [message #60062 is a reply to message #60061] |
Thu, 24 April 2008 14:42 |
peter.n.kupferman
Messages: 2
Registered: April 2008
|
Junior Member |
|
|
On Apr 24, 5:15 pm, Vince Hradil <hrad...@yahoo.com> wrote:
> On Apr 24, 3:44 pm, David Fanning <n...@dfanning.com> 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. One time it was because IDL was compiling
> and using a different file (same name) than the one I had open in the
> editor. That 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.
From 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=widget_base(/row)
wButton=widget_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
|
|
|
|
| Re: IDL Workbench Ignoring Breakpoints [message #60063 is a reply to message #60062] |
Thu, 24 April 2008 14:15 |
Vince Hradil
Messages: 574
Registered: December 1999
|
Senior Member |
|
|
On Apr 24, 3:44 pm, David Fanning <n...@dfanning.com> 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. One time it was because IDL was compiling
and using a different file (same name) than the one I had open in the
editor. That darn PATH thing...
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
