Hello all,
My question concerns the Visual C++ 6 debugger, so it’s off topic to the
WinDbg list. Sorry for that.
However, I think there might be people on this list that may know the
answer, or at least a strategy for solving the problem.
Summary:
I am debugging a user mode program on Win XP, using Visual C++6 SP5, like I
did many times before on NT4 and Win2000. As I always do, I installed the
OS symbols to %SystemRoot%\System32\Symbols. But the debugger is looking for
the symbols in the wrong place. I have never seen this behaviour before, and
would like to solve it.
When I start debugging, I get the dreaded “no matching symbolic information
found” message. Initially I thought I had a version mismatch, so I used
Windbg and its Symchk tool to check. It turns out there are no problems: I
can do symbolic debugging with WinDbg, the symbols are fine.
Next, I set the system env variable _NT_SYMBOL_PATH to
%SystemRoot%\System32\Symbols and rebooted. No change whatsoever.
Finally, I used Sysinternals’ Filemon tool to see what was going on. I found
that MSDEV.EXE is only looking for the symbol files in %SystemRoot%\System32
and the debuggee’s current directory. If I put all OS symbols there, I can
get VC++ to match and load the symbols.
So my questions are:
- has anybody seen this behaviour before? Is it user error or is it a known
bug on XP?
- what is the default debugger symbol search path?
- how can I influence this search path to make it look into
%Systemroot%\System32\Symbols
Thanks a lot,
Gert-Jan Bartelds
Hi,
This is a known problem. VC++ 6 searches for *.dbg OS symbols only. See
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q304989
Regards,
Martin
-----Original Message-----
From: Gert-Jan Bartelds [mailto:xxxxx@Fenestrae.com]
Sent: Thursday, May 16, 2002 9:08 AM
To: Kernel Debugging Interest List
Subject: [windbg] OT: VC6 debugger can’t find symbols on Win XP
Hello all,
My question concerns the Visual C++ 6 debugger, so it’s off
topic to the
WinDbg list. Sorry for that.
However, I think there might be people on this list that may know the
answer, or at least a strategy for solving the problem.
Summary:
I am debugging a user mode program on Win XP, using Visual
C++6 SP5, like I
did many times before on NT4 and Win2000. As I always do, I
installed the
OS symbols to %SystemRoot%\System32\Symbols. But the debugger
is looking for
the symbols in the wrong place. I have never seen this
behaviour before, and
would like to solve it.
When I start debugging, I get the dreaded “no matching
symbolic information
found” message. Initially I thought I had a version mismatch,
so I used
Windbg and its Symchk tool to check. It turns out there are
no problems: I
can do symbolic debugging with WinDbg, the symbols are fine.
Next, I set the system env variable _NT_SYMBOL_PATH to
%SystemRoot%\System32\Symbols and rebooted. No change whatsoever.
Finally, I used Sysinternals’ Filemon tool to see what was
going on. I found
that MSDEV.EXE is only looking for the symbol files in
%SystemRoot%\System32
and the debuggee’s current directory. If I put all OS symbols
there, I can
get VC++ to match and load the symbols.
So my questions are:
- has anybody seen this behaviour before? Is it user error or
is it a known
bug on XP?
- what is the default debugger symbol search path?
- how can I influence this search path to make it look into
%Systemroot%\System32\Symbols
Thanks a lot,
Gert-Jan Bartelds
You are currently subscribed to windbg as: xxxxx@swyx.com
To unsubscribe send a blank email to %%email.unsub%%
Martin,
Thanks for your reply. I had searched the knowledge base but this article
didn’t show up. Wrong keywords maybe… 
It works now.
Gert-Jan
-----Original Message-----
From: Hueser, Martin [mailto:xxxxx@swyx.com]
Sent: donderdag, mei 16, 2002 2:11 PM
To: Kernel Debugging Interest List
Subject: [windbg] RE: OT: VC6 debugger can’t find symbols on Win XP
Hi,
This is a known problem. VC++ 6 searches for *.dbg OS symbols only. See
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q304989
Regards,
Martin
-----Original Message-----
From: Gert-Jan Bartelds [mailto:xxxxx@Fenestrae.com]
Sent: Thursday, May 16, 2002 9:08 AM
To: Kernel Debugging Interest List
Subject: [windbg] OT: VC6 debugger can’t find symbols on Win XP
Hello all,
My question concerns the Visual C++ 6 debugger, so it’s off
topic to the
WinDbg list. Sorry for that.
However, I think there might be people on this list that may know the
answer, or at least a strategy for solving the problem.
Summary:
I am debugging a user mode program on Win XP, using Visual
C++6 SP5, like I
did many times before on NT4 and Win2000. As I always do, I
installed the
OS symbols to %SystemRoot%\System32\Symbols. But the debugger
is looking for
the symbols in the wrong place. I have never seen this
behaviour before, and
would like to solve it.
When I start debugging, I get the dreaded “no matching
symbolic information
found” message. Initially I thought I had a version mismatch,
so I used
Windbg and its Symchk tool to check. It turns out there are
no problems: I
can do symbolic debugging with WinDbg, the symbols are fine.
Next, I set the system env variable _NT_SYMBOL_PATH to
%SystemRoot%\System32\Symbols and rebooted. No change whatsoever.
Finally, I used Sysinternals’ Filemon tool to see what was
going on. I found
that MSDEV.EXE is only looking for the symbol files in
%SystemRoot%\System32
and the debuggee’s current directory. If I put all OS symbols
there, I can
get VC++ to match and load the symbols.
So my questions are:
- has anybody seen this behaviour before? Is it user error or
is it a known
bug on XP?
- what is the default debugger symbol search path?
- how can I influence this search path to make it look into
%Systemroot%\System32\Symbols
Thanks a lot,
Gert-Jan Bartelds
You are currently subscribed to windbg as: xxxxx@swyx.com
To unsubscribe send a blank email to %%email.unsub%%
You are currently subscribed to windbg as: xxxxx@fenestrae.com
To unsubscribe send a blank email to %%email.unsub%%