How do I find a node in a vi by its number?

[AnthonV]

I got an error message stating that node 0x8b4d4 caused an exception.  This could be any of the several 3rd party dll's that I am calling but I need to know which one, so I would like to find this node on the vi diagram.  Is there any way of asking LabVIEW to show me this node given the node number. 

No this error doesn't happen often enough to find using breakpoints or code watches etc - I've been waiting a few weeks for this to happen so it would be great to find this node!

[tst]

See here.

[parthabe]

tst,

You ve really provided a vital link for the Insane Objects.

I m using LV 7.1. It occasionally shows Insane Objects whan I play with swapping between Replace Array Subset & Delete From Array.

Will this tool help me in finding the exact node for the cause of the abrupt closing of LV when such an error occurs ?

Please see the link below & explain me more.

http://forums.ni.com/ni/board/message?board.id=170&message.id=201906#M201906

[AnthonV]

Thanks tst, this is interesting but unfortunately the node that I am looking for seems to be a typed as a 'list' in the heappeek app.  When you press 'F' it doesn't show you where it is in the diagram (as it would do for Teminals and others).  I've attached a grab of the heappeek app's window in case this helps. 

Any other ideas?

[tst]

Your image wasn't attached, since you linked to the file on your hard drive. You need to upload the file.

In any case, I don't have any real experience with the object browser, so I have no idea what a list is (an array wire?), but as far as I know, that's the only way to see the actual addresses of the VI elements.

The LAVA forums has a wiki which should also contain an article with some more extensive text about this tool (search for "insane"). It might explain it there.

[AnthonV]

Sorry - I've 'attached' the image this time (curse the 'Insert an Image' button!).

OK so my original question still stands to anyone out there - how do I find a node that caused an exception on the diagram.  It has to be one of several DLL calls and I wont be able to repeat it now (that is until the next demo or customer visit).  All I have is its node number as reported by the exception message that popped up at runtime.  It does not have anything to do with insane objects it seems.

The object browser is getting me closer to the answer and I'll look at the wiki for additional information.

Thanks tst.