VI Enters Debug Mode

[Spencer]

I've written after using the debugger, I finally have it working like I
want it to, but now whenever the VI is run it pauses (opens the diagram
and enters debug mode) about half way through the execution. I'm not
sure what I've done. There are no active breakpoints, and nothing in
the code that would seem to make it stop there, but I can't make it go
away. Has this happened to anyone else out there? Any ideas on what I
can try?

Thanks

Spencer
spencerwa@hotmail.com


Sent via Deja.com http://www.deja.com/
Before you buy.

[Kevin_work]

Spencer wrote:

> I've written after using the debugger, I finally have it working like I
> want it to, but now whenever the VI is run it pauses (opens the diagram
> and enters debug mode) about half way through the execution. I'm not
> sure what I've done. There are no active breakpoints, and nothing in
> the code that would seem to make it stop there, but I can't make it go
> away. Has this happened to anyone else out there? Any ideas on what I
> can try?
>
> Thanks
>
> Spencer
> spencerwa@hotmail.com
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.

Not quite sure I understand, but here are a couple of things.
Have the diagram open when the VI runs, If a section of the code
is flashing and / or has a red box around it then there is a breakpoint
aro
und that section.

If there are subVIs check to make sure that they do not have the pause
button pressed and or breakpoints set.

Make sure you do not have any infinite while loops. These can be caused
by global / local race conditions, booleans stuck in the wrong state and
hardcoded booleans

If all else fails turn on highlight execution and watch the data flow. This
should show
where the VI is hanging up.

Kevin Kent

[Jeff Miller]

Look at the front panel of your VI. Pull down the 'operate' menu item. Check
to see if 'suspend when called' is checked. Make sure it is NOT checked.

[Spencer]

In article <393fdf82@newsgroups.ni.com>,
"Jeff Miller" wrote:
>
> Look at the front panel of your VI. Pull down the 'operate' menu
item. Check
> to see if 'suspend when called' is checked. Make sure it is NOT
checked.
>

Thanks for your help, Jeff and Kent. It turns out there was a
breakpoint set, but I couldn't see it. I found it by removing small
portions of my code at a time. When I deleted a string constant the
resulting bad wire showed a breakpoint on it. I don't know why it
didn't show up when the wire was good, but it didn't. I'm still a
little puzzled as to why it happened, but at least its working now.

Spencer


Sent via Deja.com http://www.deja.com/
Before you buy.

[Greg_McKaskle2]

> > Look at the front panel of your VI. Pull down the 'operate' menu
> item. Check
> > to see if 'suspend when called' is checked. Make sure it is NOT
> checked.
> >
>
> Thanks for your help, Jeff and Kent. It turns out there was a
> breakpoint set, but I couldn't see it. I found it by removing small
> portions of my code at a time. When I deleted a string constant the
> resulting bad wire showed a breakpoint on it. I don't know why it
> didn't show up when the wire was good, but it didn't. I'm still a
> little puzzled as to why it happened, but at least its working now.
>

Not that you need my help anymore, but I believe you can also choose
Find from the
menubar and using the ring have it search for breakpoints. Then double
click to
select the item that has a breakpoint set.

Greg McKaskle

[Ultimate G]

> Not that you need my help anymore, but I believe you can also choose
> Find from the
> menubar and using the ring have it search for breakpoints. Then double
> click to select the item that has a breakpoint set.
>
> Greg McKaskle
>

LabVIEW should offer a one-shot menu item to remove all breakpoints in a VI
without having to search for, and remove manually, each one individually.

Regards -

Mark Evans
Ultimate G - Power tools for LabVIEW
http://www.UltimateG.com


Sent via Deja.com http://www.deja.com/
Before you buy.