LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

general protection fault gui runuserinterface

I currently have LabWindows 9.01 running on my computer.  I am writing a test automation program that uses GPIB to talk to several instruements.  I am having problems running my code because it will sometimes run into a general protection fault.  I suspect that it may have something to do with the GUI because the code crashes at the line where I call RunUserInterface ();  The crash report from windows is:

*----> State Dump for Thread Id 0x2fc <----*

eax=64501090 ebx=01fe0050 ecx=7c912d78 edx=ffffffff esi=0000023c edi=00000000
eip=7c90e514 esp=0217fee0 ebp=0217ff44 iopl=0         nv up ei pl zr na po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000246

function: ntdll!KiFastSystemCallRet
        7c90e4fa e829000000       call    ntdll!RtlRaiseException (7c90e528)
        7c90e4ff 8b0424           mov     eax,[esp]
        7c90e502 8be5             mov     esp,ebp
        7c90e504 5d               pop     ebp
        7c90e505 c3               ret
        7c90e506 8da42400000000   lea     esp,[esp]
        7c90e50d 8d4900           lea     ecx,[ecx]
        ntdll!KiFastSystemCall:
        7c90e510 8bd4             mov     edx,esp
        7c90e512 0f34             sysenter
        ntdll!KiFastSystemCallRet:
        7c90e514 c3               ret
        7c90e515 8da42400000000   lea     esp,[esp]
        7c90e51c 8d642400         lea     esp,[esp]
        ntdll!KiIntSystemCall:
        7c90e520 8d542408         lea     edx,[esp+0x8]
        7c90e524 cd2e             int     2e
        7c90e526 c3               ret
        7c90e527 90               nop
        ntdll!RtlRaiseException:
        7c90e528 55               push    ebp
        7c90e529 8bec             mov     ebp,esp

*----> Stack Back Trace <----*
WARNING: Stack unwind information not available. Following frames may be wrong.
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\WINDOWS\system32\NIPALU.dll -
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\WINDOWS\system32\ni4882.dll -
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\WINDOWS\system32\nipalut.
dll -
ChildEBP RetAddr  Args to Child             
0217ff44 7c802532 0000023c ffffffff 00000000 ntdll!KiFastSystemCallRet
0217ff58 6402f6ce 0000023c ffffffff 01f201cc kernel32!WaitForSingleObject+0x12
0217ff70 6402f68f ffffffff 0217ff94 6abccfce NIPALU!tThreadUtility__getCurrentThreadId+0xa4e
0217ff7c 6abccfce ffffffff 0217ff90 01fe0040 NIPALU!tThreadUtility__getCurrentThreadId+0xa0f
0217ff94 6450113e 01fe0050 01c1eae4 7c90e920 ni4882!WaitSRQ+0x23fce
0217ffb4 7c80b699 00000001 01c1eae4 7c90e920 nipalut!threadMainWin32+0xae
0217ffec 00000000 64501090 00186dd8 00000000 kernel32!GetModuleFileNameA+0x1ba


*----> State Dump for Thread Id 0xf4c <----*

eax=64501090 ebx=01fe009c ecx=7c912d78 edx=ffffffff esi=0000027c edi=00000000
eip=7c90e514 esp=021cfed4 ebp=021cff38 iopl=0         nv up ei pl zr na po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000246

function: ntdll!KiFastSystemCallRet
        7c90e4fa e829000000       call    ntdll!RtlRaiseException (7c90e528)
        7c90e4ff 8b0424           mov     eax,[esp]
        7c90e502 8be5             mov     esp,ebp
        7c90e504 5d               pop     ebp
        7c90e505 c3               ret
        7c90e506 8da42400000000   lea     esp,[esp]
        7c90e50d 8d4900           lea     ecx,[ecx]
        ntdll!KiFastSystemCall:
        7c90e510 8bd4             mov     edx,esp
        7c90e512 0f34             sysenter
        ntdll!KiFastSystemCallRet:
        7c90e514 c3               ret
        7c90e515 8da42400000000   lea     esp,[esp]
        7c90e51c 8d642400         lea     esp,[esp]
        ntdll!KiIntSystemCall:
        7c90e520 8d542408         lea     edx,[esp+0x8]
        7c90e524 cd2e             int     2e
        7c90e526 c3               ret
        7c90e527 90               nop
        ntdll!RtlRaiseException:
        7c90e528 55               push    ebp
        7c90e529 8bec             mov     ebp,esp

*----> Stack Back Trace <----*
WARNING: Stack unwind information not available. Following frames may be wrong.
ChildEBP RetAddr  Args to Child             
021cff38 7c802532 0000027c ffffffff 00000000 ntdll!KiFastSystemCallRet
021cff4c 6402f6ce 0000027c ffffffff 01ff0040 kernel32!WaitForSingleObject+0x12
021cff64 6402f68f ffffffff 021cff94 6abbb0be NIPALU!tThreadUtility__getCurrentThreadId+0xa4e
021cff70 6abbb0be ffffffff 021cff90 01fe009c NIPALU!tThreadUtility__getCurrentThreadId+0xa0f
021cff94 6450113e 01fe009c 01c1eb34 7c90e920 ni4882!WaitSRQ+0x120be
021cffb4 7c80b699 00000001 01c1eb34 7c90e920 nipalut!threadMainWin32+0xae
021cffec 00000000 64501090 00186dd8 00000000 kernel32!GetModuleFileNameA+0x1ba

Thank you for your help.
0 Kudos
Message 1 of 3
(3,692 Views)

Hello Carrot826,

 

Could you please follow the steps outlined here and post the resulting .dmp file to ftp://ftp.ni.com/incoming?  Also, if you could let us know what build version of CVI you are using (9.0.1.XXX), that will enable us to read the crash dump.  

 

Can you make any generalizations about what is going on when the program crashes?  Does it happen when waiting for user input, or immediately after some type of user interaction has occurred?  Is your application multi-threaded?  Any more description of the application you can give will also be helpful.

 

One final thing that would be helpful to include with the crash dump is a map file of your application, generated just prior to running it until it crashed. 

 

When you've got it up on the ftp site, let me know the name of the zip file you've uploaded, and I'll take a look.

 

Thanks!

 

NickB

National Instruments  

0 Kudos
Message 2 of 3
(3,664 Views)

I orginally began my project using labwindows 8.5 and then upgraded to 9.0.  I just reinstalled 8.5 and ran my code and saw that the function GetTableCellFromValue no longer returned the correction cell location.  The executable no longer crashes when I bulid using 8.5.  I orginally used the function to return the location of a cell with a particular value.  Can this functino cause a GUI memory leak?

 

Thanks.

0 Kudos
Message 3 of 3
(3,650 Views)