How do we debug lvlibp which is involved by a .exe file

[悟啊呀呀]

When I debug a debug-enabled lvlibp which is called by a source code A, I can set breakpoint in a *.lvlibp:VI and the breakpoint is valid. But the breakpoint is invalid when I build the source code A to A.exe. It seems like that a copy of lvlibp is running. How do I debug the lvlibp file which is involved by a executable file.

Thanks!

[crossrulz]

Operate->Debug Application Or Shared Library...

That will open up a dialog allowing you to connect to an application to debug it.

[JÞB]

---

@悟啊呀呀 wrote:

When I debug a debug-enabled lvlibp which is called by a source code A, I can set breakpoint in a *.lvlibp:VI and the breakpoint is valid. But the breakpoint is invalid when I build the source code A to A.exe. It seems like that a copy of lvlibp is running. How do I debug the lvlibp file which is involved by a executable file.

Thanks!

---

You should not be debugging a packed library!  in fact it should have been documented and the test artifacts should trace the requirements to whatever requirements are met by the PPL!  

That being said, what Version of LabVIEW is used?  Some changes have been made to names recently when building PPLs. (still trying to understand all of them myself) a Nugget would be nice

\/\/\/\/\/\

[悟啊呀呀]

Hi, crossrulz. It's worked! Thank you!

May I ask you another question?

When I run the application debug mode, I can open the block diagram to trace my problem. How can I open a VI which is called dynamically by its path? Now, I have to open the Tools->Profile->Performance and memory to find the VI I needed. Do you have any convenient way?