Quantcast
Channel: VMware Communities : Popular Discussions - VIX API
Viewing all articles
Browse latest Browse all 34639

My program crashes in VIX with: Access violation reading location

$
0
0

Hi,

 

My C# program that uses the VIX API keeps crashing. I'm trying to use VIX 1.2.6 to connect to ESXi 3.5.0.

The crash usually seems to happen after I kick off a job and while I'm waiting for it to complete with a call to IJob.Wait or IJob.WaitWithoutResults, or polling in a loop with a pause calling IJob.CheckCompletion.

 

I got the following from the debugger:

 

Unhandled exception at 0x068f58ba in MyProgram.exe: 0xC0000005: Access violation reading location 0x00000008.

 

Call stack:

>     gvmomi.dll!068f58ba()      

     http://Frames below may be incorrect and/or missing, no symbols loaded for gvmomi.dll     

     gobject-2.0.dll!03e4718c()      

     glib-2.0.dll!04b4b0d8()      

     glib-2.0.dll!04b4b44e()      

     gobject-2.0.dll!03e44f7f()      

     gobject-2.0.dll!03e47926()      

     vix.dll!11119135()      

     vix.dll!11119150()      

     vix.dll!111070ab()      

     vix.dll!111079ca()      

     vix.dll!1110394d()      

     vix.dll!1115f23f()      

     vix.dll!1115fa93()      

     vix.dll!1110198d()      

     vix.dll!11191380()      

     kernel32.dll!7628d0e9()      

     ntdll.dll!777119bb()      

     ntdll.dll!7771198e()      

 

Disassembly:

068F58AD  int         3   

068F58AE  int         3   

068F58AF  int         3   

068F58B0  push        ebp 

068F58B1  mov         ebp,esp

068F58B3  mov         eax,dword ptr

068F58B6  push        esi 

068F58B7  mov         esi,dword ptr

068F58BA  mov         ecx,dword ptr       <-- current instruction

068F58BD  push        edi 

068F58BE  mov         edi,dword ptr

068F58C1  push        edi 

068F58C2  push        ecx 

068F58C3  call        06A7B39A

068F58C8  add         esp,8

068F58CB  test        eax,eax

068F58CD  je          068F58EA

068F58CF  mov         edx,dword ptr

068F58D2  push        eax 

068F58D3  push        edx 

068F58D4  call        06A7B3BE

068F58D9  mov         eax,dword ptr

068F58DC  push        edi 

068F58DD  push        eax 

068F58DE  call        06A7B3BE

068F58E3  add         esp,10h

068F58E6  pop         edi 

068F58E7  pop         esi 

068F58E8  pop         ebp 

068F58E9  ret             

068F58EA  push        6A7D310h

068F58EF  push        1DBh

068F58F4  push        6A7D2B4h

068F58F9  push        6A7C500h

068F58FE  push        8   

068F5900  push        0   

068F5902  call        06A7B388

068F5907  add         esp,18h

068F590A  pop         edi 

068F590B  pop         esi 

068F590C  pop         ebp 

068F590D  ret             

068F590E  int         3   

068F590F  int         3   

068F5910  push        ebp 

068F5911  mov         ebp,esp

068F5913  mov         eax,dword ptr

068F5916  push        ebx 

068F5917  mov         ebx,dword ptr

068F591A  test        ebx,ebx

068F591C  push        esi 

068F591D  push        edi 

 

Also, I'm not quite sure why. Although I'm debugging my program in VS2008, when the crash occurs, I get another dialog that pops up with the crash and asks me to select a debugger. If I look through code in the debugger I originally had running, I can't find the failure or call stack. From the dialog though, if I select to start a new debugger I can get the above information.

 

 

Please, can anybody help?

 

Thanks very much,

  Scott


Viewing all articles
Browse latest Browse all 34639

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>