LabVIEW Debugging Window

[jgcode]

I had never seen this Window before until the other day.

It just popped up, couldn't do much with it - I am guessing it is an internal LabVIEW thing?

Anyone seen it before?

[MikaelH]

No, do you have any extra "debugging keys setup in your LabVIEW.ini file.

[jgcode]

No, do you have any extra "debugging keys setup in your LabVIEW.ini file.

Negative.

I was working with some code calling dll's, the only difference was this popped up on my 64-bit OS install but not my 32-bit OS install (both Win7 with 32-bit LabVIEW 2009).

[asbo]

Nope, never seen it before. Is it reproducible?

[mathilde38]

This window can be called by a CIN code, by using the function

DbgPrintf("Value to debug : %d", value);

Is is very useful to debug CIN functions.

It is defined in the /LabVIEW folder/cintools/extcode.h

[jgcode]

This window can be called by a CIN code, by using the function

DbgPrintf("Value to debug : %d", value);

Is is very useful to debug CIN functions.

It is defined in the /LabVIEW folder/cintools/extcode.h

Thx - that would explain it

[jcarmody]

I finish reading this thread, pop over to try something and experience the same thing.

[Charlie Murdock]

Can anyone explain to me how to get that debugging window? I am trying some CIN's, dll's, scripting methods, but I can't get that...

Please give me some tips or simple VI with something like printf function in dbg window.

[Yair]

Well, according to what it says, you can get it by calling a specific function from a CIN, but you should keep in mind that CINs are generally legacy tech, so it's possible that something would have stopped working in newer versions. Personally I never saw this window, but I don't really use CINs.

 

If you want a simple debug window, you can do something as simple as VI which takes in a string input and concatenates it to a string indicator, which is the log. You set the VI to show the FP when called and you're done. Of course, you could get a lot fancier with loggers and debuggers and have levels, daemons, logging to disk, etc. There are various loggers available online.

[Darin]

Not CIN specific.

 

 

just select LabVIEW in the CLFN, mgErr is typedef'ed as an I32 in extcode.h

[hooovahh]

Not CIN specific.

 

just select LabVIEW in the CLFN, mgErr is typedef'ed as an I32 in extcode.h

I couldn't get your snippet to work, can someone else confirm that something was lost in the upload?

[Darin]

My original file is 10.1 kBytes and the downloaded one is 4.16 so it appears something is stripped out.

 

to recreate:

 

1) drop a CLFN, choose 'LabVIEW' as the library name and click run in any thread.

2) make the output parameter a 32-bit signed integer

3) add a string input parameter with default settings.

4) wire and enjoy.

 

I kind of like it sometimes when debugging myself.  I am always closing a BD window and killing probes.