Showing results for 
Search instead for 
Did you mean: 
Reply

Exploiting Win32 OutputDebugString() using LabVIEW

Solved!
Go to Solution

Exploiting Win32 OutputDebugString() using LabVIEW

Is it possible to implement debugging facility using Win32 OutputDebugString() API's in LabVIEW?

0 Kudos
Reply
0 Kudos

Re: Exploiting Win32 OutputDebugString() using LabVIEW

I don't really see how, as there is no debugger, per se, in LabVIEW in the sense that that function expects.

0 Kudos
Reply
0 Kudos
Highlighted

Re: Exploiting Win32 OutputDebugString() using LabVIEW

What I meant is, the LabVIEW application should keep posting messages using the OutputDebugString() API so that some debugger program like Dbwin32 can capture the messages and display it. If that can be implemented, it will serve as a mechanism to observe what the LabVIEW application is doing now and also it will behave like a probe so that we can utilize it as a debugging tool.

0 Kudos
Reply
0 Kudos

Re: Exploiting Win32 OutputDebugString() using LabVIEW

Well, I suppose you can try calling it using the Call Library Function Node. The prototype for it is pretty simple - it just has a single string input.

0 Kudos
Reply
0 Kudos
Solution
Accepted by topic author Flamboyant
‎08-27-2015 06:09 PM

Re: Exploiting Win32 OutputDebugString() using LabVIEW

0 Kudos
Reply
0 Kudos