LabView Stack Trace or Call Stack / Tracing

[geirove]

Hello,

I am using LabView 8.0.

I am becoming utterly frustrated by not being able to see **who** is calling the code where I set a break point. All programming languages with a Debugger can show you WHO called a method / function when you set a breakpoint there, but not LabView ?

I have developed an error in a system whereas "some code" is setting an unwanted state of a switch, I can set a breakpoint there and see that it happens, but I cannot find out who the caller is !

Please help !

Geir Ove

[rolfk]

---

@geirove wrote:

Hello,

I am using LabView 8.0.

I am becoming utterly frustrated by not being able to see **who** is calling the code where I set a break point. All programming languages with a Debugger can show you WHO called a method / function when you set a breakpoint there, but not LabView ?

I have developed an error in a system whereas "some code" is setting an unwanted state of a switch, I can set a breakpoint there and see that it happens, but I cannot find out who the caller is !

Please help !

Geir Ove

---

Have you ever taken a look at the drop down box that is normally used to select fonts in edit mode? Try it and tell me if you are still that frustrated!

Rolf Kalbermatter

[geirove]

Thanks but, still Frustrated ! More Info: I  am trying to track the Source of an Event:

I have SubVi's that use the "Property Value (signalling)" to fire Events in the Top VI: I am setting a breakpoint in the Top VI and it will break when someone is setting a Value for e.g. a Button by e.g. writing a True value to "Property Value (signalling)" in a SubVi.

Problem is I will not get any Stack trace the way suggested here for the Events ....

Any solution to this problem ?

Geir Ove

[Ben]

The source of the event will not be on the call stack or available anywhere I know of.

Events are one way animals that get queued up to the event structure and handled in order (as far as I have observed). There is no feed-back to to the entity that initiates the event that it has occured so there is no reason to drag that info around.

Back to helping you.

It sounds like you have the posibility of updateing a value from more than one place at some time(s).

If so, this is what is concidered a Race Condition. If you are frustrated trying to fix this I am not suprised.   Try to make a race condition work can be an exercise in futility.

To save you more greif, I would like to invite you to post your code so we can advise on how to proceed.

Ben

Message Edited by Ben on 02-14-2007 06:45 PM

[geirove]

Hello,

Well there is nothing wrong with the code per se. The switches are simulating Motor on / off relays that in a real system of course can be turned on and off from more than one place !

The code is the customer's property so it cannot be posted here, and the size of it is way to big to post anyway.

The problem here is that LabView has no way of tracing the soruce of an event, which I can do perfectly well in e.g. Java.

The code is quite clean, so it did not take long to track down the offending party.

I just wanted to see what LV could do to help tracking this kind of problem. In the future I will avoid events for this kind of actions.

However, I am dissapointed with the debugging facilities in LV compared to other modern programming environments that I have used.

[Ben]

THis is a cross posting with LAVA

http://forums.lavag.org/index.php?showtopic=6283&pid=24406&st=0&#entry24406

See that thread for more ideas on how to track events back to their source.

They all require explicit code to suppor tthe tracking.

Ben

[Darren]

And in the future geirove, please don't cross-post between the NI Forums and LAVA...and if you do, at least indicate that you have done so by including a link in one message to the other thread you started.  Some of us duplicated effort giving you the same responses that you already received from someone else in both forums.

-D

[geirove]

Hello ,

Thanks everyone for all your help!  I was not aware that there was so much "cross traffic" between these forums. I will obey the rules.