Prev: Create status bar
Next: Combo Box Special Style
From: chhenning on 16 Feb 2010 12:06
Alright, here we go again. The problem reappeared. I was able to
create a simple console app ( x64 ) which loads my troubling COM DLL
into the memory. After this is done I use my debug code ( some very
basic file io ) and it fails when calling fflush. I get an endless
stream of

First-chance exception at 0x8018c480 in engine_harness_2.exe:
0xC0000005: Access violation at location 0x000000008018c480.


Now, I have learned somethings from the last time. I have installed
Application Verifier ( x64 version ) and trying to see what's going
on. Interestingly when I attach my troubling app to the AppVerifier it
runs through without any problems. This now is more than strange. Can
someone tell me what the AppVerifier does? BTW, all logs that
AppVerifier is suppose to create are all empty.

All I can see in the debug output is this:

'engine_harness_2.exe': Loaded 'C:\chh\projects
\engine_harness_2\x64\Debug\engine_harness_2.exe', Symbols loaded.
'engine_harness_2.exe': Loaded 'D:\WINDOWS\system32\ntdll.dll', No
symbols loaded.
Page heap: pid 0x1308: page heap enabled with flags 0x3.
AVRF: engine_harness_2.exe: pid 0x1308: flags 0x80443027: application
verifier enabled
'engine_harness_2.exe': Loaded 'D:\WINDOWS\system32\verifier.dll', No
symbols loaded.
AVRF: failed to initialize verifier logging (C000003A).
AVRF: verifier.dll provider initialized for engine_harness_2.exe with
flags 0x80443027
'engine_harness_2.exe': Loaded 'D:\WINDOWS\system32\vrfcore.dll', No
symbols loaded.
[snip]

I keep getting the message "AVRF: failed to initialize verifier
logging (C000003A)." Why is that? I'm debugging a x64 process with x64
AppVerifier.

Any help is more than welcome.

Thanks,
Christian
From: chhenning on 18 Feb 2010 15:55
OK, finally some movement! I have attached my program to WinDbg and it
seems the problem is with a function called DebuggerProbe from inside
MSVCR80D.DLL. This evidence led me directly to the following bug
report:

https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=100319&wa=wsignin1.0

The problem described here is very similar to what I'm experiencing.
Besides the fact that the reporter's program is aborting and my
program is endlessly issuing these first hand exceptions. I'm not sure
what to do next. Any ideas?

Thanks,
Christian
First  |  Prev  | 
Pages: 1 2
Prev: Create status bar
Next: Combo Box Special Style