Finding VI Clones

[mje]

If I'm debugging a VI clone, I can easily find the original by using View: Browse Relationships: Reentrant Original. But is there a way to do the opposite? Given an original VI, I'd like to see the list of clones currently in memory.

[Jordan Kuehn]

I didn't go back through and read it again, but this thread might be helpful:

[Aristos Queue]

mje: The short answer is "no". Not programmatically, and not through the UI. Cloning was never designed to support that use case.

[mje]

That other thread is interesting, but I was looking for a native UI option.

Thanks AQ. No big deal, clones can easily be found by digging through a few layers of VIs and opening them from the block diagrams.

[Aristos Queue]

"Easily?" Really? I'm going to have to hire you for my next debugging session. I've been using terms like "frustrating", "maddening" and "the sort of exercise that drives programmers to contemplate text."

[mje]

Hahaha. I was being civil. Frustrating indeed, especially when you're dealing with multiple levels of reentrancy. Don't get me going though on dynamically allocated clones, the feds ought to give up waterboarding and just have detainees attempt to debug those applications...

[crelf]

"the sort of exercise that drives programmers to contemplate text."

whoa Whoa WHOA! That's crazy talk right there!

[John Lokanis]

I believe if you set a breakpoint in the original, you can cause all the clones to halt at that breakpoint and give you access to them. Kinda annoying but it should work.

I too have longed for a clone browser and tried to implement one but failed...

[asbo]

I can't test it right now, but what about a conditional probe in the master VI?

[Ton Plomp]

John's idea is something I found out last week. It's quite good. A conditional probe in the master VI won't work, since the code isn't running. But you can create a conditional probe (before running) in your master VI with a breakpoint.

Ton