LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

Possible bug - Print functionality from YGraphPopup broken in 64 bit?

Solved!
Go to solution

Hello All,

 

I occasionally use the YGraphPopup to debug my programs. Today I tried to use the built-in "Print" button functionality and I got a GP Fault. Has anyone tried this functionality under CVI 2012 64-bit?

 

I think there is a problem there. (32 bit code brings up a printer dialog box on same code that 64 bit throws the GP fault.) XGraphPopup displays similar issues.

 

I will post a simple program for anyone that wants to try.

 

 

Windows 7 Enterprise SP1

CVI FDS Version 12.0.0 (422)

0 Kudos
Message 1 of 6
(3,814 Views)

Hi blakney,

 

I ran the files you attached on a Windows 7 Enterprise SP1 OS using CVI FDS 2012, but did not encounter an error. Would it be possible that there is an issue communicating with the specific printer using the new OS? I found a few instances of a GP fault with Windows 7 64 bit, including the following:  http://windowssecrets.com/forums/showthread.php/138583-Printer-properties-causes-general-protection-...

 

Regards,

 

Jason D

Applications Engineer

National Instruments

0 Kudos
Message 2 of 6
(3,786 Views)

Just to make sure we are doing the same exercise.

 

The matrix all performed on my Windows 7 OS machine on CVI 2012 FDS is as follows.

 

I can compile the code with four options (debug32, release32, debug64, and release64). Each will compile and run. I hit the test command button and the Ygraphpopup / Xgraphpopup

will display as expected with two command button "OK" and "Print". OK command button works fine in all cases (and closes the graph).

 

Pressing the Print command button works as expected for the Debug32 and Release32 cases and opens a print dialog box. This dialog box will produce a hard copy just fine.

 

Pressing the Print command button immediately fails for the debug64 and release64 cases and generates either General Protection faults(debug64) / closes the program (release64).

 

In detail, when I compile the provided code as

 

Debug (meaning 32 bit build) - works as expected.

Release (meaning 32 bit build) - works as expected.

 

Debug64 - Fatal Run-Time Error

                "main.c" line 49, col 13, thread id 0x00002E28

                The program has caused a a 'General Protection' fault at 0x00000000687A8DD

Release64 - YGraphCheck (Release x64) has stopped working

                Windows is collecting more information about the problem.

                This might take several minutes...

 

If requested, I will post the Windows error logs generated.

 

Message 3 of 6
(3,774 Views)
Solution
Accepted by topic author blakney

Hi blakney,

 

Thank you for providing the extra information to reproduce the issue! This was reported to R&D (#396168) for further investigation. Are you looking for a workaround as well?

 

Regards,

 

Jason D

Applications Engineer

National Instruments

0 Kudos
Message 4 of 6
(3,756 Views)

As I just use this for debugging on occasion, it is not worth trying to find a workaround. I just thought I would put it in the queue for version 13.0 😉

0 Kudos
Message 5 of 6
(3,739 Views)

Hi blakney,

 

This issue has definitely been reported now; thank you for letting us know! As an aside, we have released LabWindows/CVI on a 2 year cycle in the past. I hope your programming goes smoothly!

 

Regards,

 

Jason D

Applications Engineer

National Instruments

0 Kudos
Message 6 of 6
(3,729 Views)