Discussion:
No type information found for `_AVRF_EXCEPTION_LOG_ENTRY'
(too old to reply)
RolfeM
2007-05-11 19:01:01 UTC
Permalink
Is this a known issue? How do I get around it?
I'm using Application Verifier version 3.3.0045 and Windbg 6.6.0007.5 on XP
Pro Sp2.
Thanks.

Detailed Error Message:
0:004> !avrf
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: vfbasics!_AVRF_EXCEPTION_LOG_ENTRY ***
*** ***
*************************************************************************
No type information found for `_AVRF_EXCEPTION_LOG_ENTRY'.

This extension requires symbols with type information
for ntdll.dll and verifier.dll.

Please fix the symbols for `[verifier core DLL]'.
Dan Mihai [MSFT]
2007-05-11 21:06:20 UTC
Permalink
Is c:\windows\system32 part of your symbols path, in the debugger? If I
remember correctly, that's where vfbasics.pdb should be present.

Dan
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Post by RolfeM
Is this a known issue? How do I get around it?
I'm using Application Verifier version 3.3.0045 and Windbg 6.6.0007.5 on XP
Pro Sp2.
Thanks.
0:004> !avrf
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: vfbasics!_AVRF_EXCEPTION_LOG_ENTRY
***
*** ***
*************************************************************************
No type information found for `_AVRF_EXCEPTION_LOG_ENTRY'.
This extension requires symbols with type information
for ntdll.dll and verifier.dll.
Please fix the symbols for `[verifier core DLL]'.
RolfeM
2007-05-11 23:16:01 UTC
Permalink
Thanks. You helped me to find my mistake. My symbol path included the
Microsoft symbol server first then the system32 folder second. When I
changed the order and put system32 first the error went away.
Post by Dan Mihai [MSFT]
Is c:\windows\system32 part of your symbols path, in the debugger? If I
remember correctly, that's where vfbasics.pdb should be present.
Dan
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Post by RolfeM
Is this a known issue? How do I get around it?
I'm using Application Verifier version 3.3.0045 and Windbg 6.6.0007.5 on XP
Pro Sp2.
Thanks.
0:004> !avrf
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: vfbasics!_AVRF_EXCEPTION_LOG_ENTRY
***
*** ***
*************************************************************************
No type information found for `_AVRF_EXCEPTION_LOG_ENTRY'.
This extension requires symbols with type information
for ntdll.dll and verifier.dll.
Please fix the symbols for `[verifier core DLL]'.
Loading...