LabVIEW 2015 debug of Executable doesn't respect Break points

[Jeannius]

I notice that when I try to debug an executable in LabView 2015, it goes right through the breakpoints like they don't exist.

I have created a small project to demonstrate this.

Download it and build the executable. Open the exe file, It is set to not run when you launch.

From there you can try to debug it.

Looking at the actual code you can clearly see that the Actor Core vi has a break point. Said break point execute fine if you run the vi in the project, but is completely ignored if you debug the executable.

I am almost certain (though I may be wrong) that LabVIEW 2014 allowed you to have break points in executable.

Am I missing something?

Please help.

[AristosQueue (NI)]

We have never allowed breakpoints in executables. Executables don't even have the ability to load block diagrams. You can save the diagrams in the executable and then attach a debugger (remote debugging). But just saving directly in the executable? Not to the best of my knowledge.

[lsi]

HI, I think that in the original post the author is doing exactly what you suggest. He creates an executable with remote debug enabled and "Wait for debugger on launch" option enabled. Then he remote debugs the so-built executable, but then the breakpoints set in the original block diagram of the source are not respected. I can confirm this behaviour now and I recall (but one can never be sure) that previously this was working.

Assuming that my memory fails me and the breakpoints set in the original source before compiling the remote debugable executable, since in the actor framework the Actor Core.vi is launched via VI server, my question is then: how can we then set breakpoints if we cannot browse the source of the code being executed?

Cheers

Andrea