debugger no blockdiagram

[WeberM]

hello,

i work with thr debugger for the first time.
my problem is that i havn't got a blockdiagramm to set probes or breakpoints. or is this not possible in labview?
i startet my executable and connected my application. there are two windows. one window is remotes the other, but there's no blockdiagramm
is there any way to open a blockdiagramm?

markus

[GerdW]

Hi Markus,

in an executable you don't have blockdiagrams of the used vi's. You have to use the development vi's to do so.

You should always mention what version of LV you use, when it comes to very tricky questions 🙂

[WeberM]

hello,

i use the developer suite 8.01.
but there are no blockdiagramms neither the remote debugging window nor the other window.
is there any manual for the debugger?
probably i have a wrong opinion.

markus

[TCPlomp]

Hi Markus,

What do you mean by 'debugger'. If you want to debug the an executable (from the project explorer: Operate>>>Debug application or DLL)  You should have this option ticked in the build of the executable (Advanced>>> Enable debugging) In that way the block diagram of the vi's are not removed and you can probe them (and use executed highlighting) like the development environment.

Ton

[dan_u]

It is possible to remove diagrams from VIs. If you downloaded the VIs or got them from someone, it is possible they removed the diagram so the "source code" can't be viewed/edited. If "Show Block Diagram" in the Window menu is greyed out, it is removed. There's no way to retrieve it. You'll have to ask the author for the original copy with diagram.
It the diagram isn't removed, just click "Ctrl-E" to display it.

[WeberM]

hello,

my executable is build with these option.
but how can i show the blockdiagramm?
i start the executable and then i start debug application or shared library.push the connect button. LV started a second application.with this application i can control the first startet executable.
so far so good.

how to display a blockdiagramm??
with "crtl + e" i can't show it.

markus

[WeberM]

hello,

i think i've found the problem.
is it possible that you can' debug with a custom run time menu???
is there any way to avoid this?
markus

[Kennon_Cotton]

Markus,

I tested out your theory and found that with a custom run-time menu CTRL-E gets ignored while the VI is running in the EXE as does the menu item Show Diagram.  The only way I found to do it is to also enable 'Wait for debugger on launch' in the EXE builder.  This will cause the EXE to open but not run any VIs until you press the run button or connect via the Operate>Debug Application and then press Run this will give you the chance to Connect, show the diagram, then click the run button.  I'll report this so it gets fixed.

Kennon

[THailey3]

Kennon did report the issue as he mentioned, but forgot to attach the bug ID, so here it is...

This was reported to R&D (# 41BAQFXC) for further investigation.

Thanks for the feedback!

[DanyAllard]

It's not corrected in LabVIEW 8.2.1. When you use a top level VI with a custom menu you can't get the block diagram of the VI. When you wait for debuger at statup of the application you can open BD but when you start your application the custom menu don't apper. I can't debug if i dont have my custom menu.

It could be nice to have a right click option to open the block diagram at any time.

Dany