First chance exception messages

[irccwh]

VAST 7.5.1, Windows
We do a lot of async platform function calls to our own dlls. When running under a VC++ debugger we occasionally see "First-chance exception in nodialog.exe (ESVM40.DLL): 0xC0000005: Access Violation." messages.

Should we expect these exceptions to occur in esvm40 code or does it generally indicate that we are doing something wrong on our end?

Thanks,
Chad

[marten]

VAST 7.5.1, Windows
We do a lot of async platform function calls to our own dlls. When running under a VC++ debugger we occasionally see "First-chance exception in nodialog.exe (ESVM40.DLL): 0xC0000005: Access Violation." messages.

Should we expect these exceptions to occur in esvm40 code or does it generally indicate that we are doing something wrong on our end?

Thanks,
Chad

Whenever I noticed exceptions within the virtual machine in my async calls (or sync calls) I made mistakes when preparing (saveing/creating) the argument values for these calls - and async calls might be much more difficult to handle than sync calls.