That sounds like a great tool. Another related idea I have had is an execution tree that shows (like the hiarchy) what VIs were called by what VIs (clone links). It would be best to show what VIs WILL be called and allow me to insert breakpoints in certain instances of reentrant VIs. But, if it has to be after the fact then allow me to use the Retain Wire Values to go back and debug a particular call to a reentrant VI.

With the push toward more parallel programming methods, debugging large VIs with lots of reentrancy, we need some much more advanced tools to debug our apps.

-John

________________________________

From: Info-LabVIEW@labview.nhmfl.gov on behalf of Stephen Mercer
Sent: Mon 8/20/2007 2:49 PM
To: Info-LabVIEW (E-mail)
Subject: Re: How about a "Execution Highlight Point"?



Execution Highlight Point... a trigger to turn on or off execution
highlighting.
Interesting. But... may I suggest a broader dream?

How about simply an "execution point trigger." Something that can be set
on a block diagram when it is running. Triggers that could
a) turn on and off execution highlighting
b) turn on and off breakpoints in your code
c) turn on and off probes
d) open or close front panels

In short, triggers that let you debug code without having to constantly
manage your own debugging. I've thought about such an array of triggers
for years, but never done anything with the idea.

Thoughts?

Pojundery,
Stephen R. Mercer
-= LabVIEW R&D =-