I’m having a bit of a tear the hair out problem with windbg 6.1.0017.0
here. To be specific its not showing me all of the local variables (makes
the debugging a bit tricky). To be specific I am looking at a full crash
dump on W2K SP3 after PAGE_FAULT_IN_NON… and what I can see is
consistent with a garbage pointer dereference. Is there some limitation is
windbg here?
If this is optimized code then some local variables may have been
optimized away…
-----Original Message-----
From: xxxxx@gcplc.com [mailto:xxxxx@gcplc.com]
Sent: Monday, February 24, 2003 11:06 AM
To: Kernel Debugging Interest List
Subject: [windbg] Windbag not showing all the locals?
I’m having a bit of a tear the hair out problem with windbg 6.1.0017.0
here. To be specific its not showing me all of the local variables
(makes the debugging a bit tricky). To be specific I am looking at a
full crash dump on W2K SP3 after PAGE_FAULT_IN_NON… and what I can see
is consistent with a garbage pointer dereference. Is there some
limitation is windbg here?
You are currently subscribed to windbg as: xxxxx@microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com
I’ve seen the same problem in unoptimized code w/ this build of the debugger.
Seems to happen more with variables that are assigned in the same line that they’re declared (e.g. “char *ptr = NULL” kind of things tend to now show in the Locals window).
-----Original Message-----
From: Nathan Nesbit [mailto:xxxxx@windows.microsoft.com]
Sent: Monday, February 24, 2003 11:51 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: Windbag not showing all the locals?
If this is optimized code then some local variables may have been
optimized away…
-----Original Message-----
From: xxxxx@gcplc.com [mailto:xxxxx@gcplc.com]
Sent: Monday, February 24, 2003 11:06 AM
To: Kernel Debugging Interest List
Subject: [windbg] Windbag not showing all the locals?
I’m having a bit of a tear the hair out problem with windbg 6.1.0017.0
here. To be specific its not showing me all of the local variables
(makes the debugging a bit tricky). To be specific I am looking at a
full crash dump on W2K SP3 after PAGE_FAULT_IN_NON… and what I can see
is consistent with a garbage pointer dereference. Is there some
limitation is windbg here?
You are currently subscribed to windbg as: xxxxx@microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com
You are currently subscribed to windbg as: xxxxx@softek.fujitsu.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
lclarke: What does !lmi show for the module you are trying to
debug / look at locals?
SMcDowell: Do you have a code snippet from a real piece of code that
demonstrates the issue? This doesn’t sound like anything we have seen.
Also a !lmi and/or a minidump of your process with matching
PDB/EXE + full source file (for line number matching) would be useful.
If you have problems with the Windows debuggers I recommend you post the
issues to the microsoft.public.windbg newsgroup.
David Holcomb
Microsoft
-----Original Message-----
From: McDowell, Steve [mailto:xxxxx@softek.fujitsu.com]
Sent: Monday, February 24, 2003 12:08 PM
To: Kernel Debugging Interest List
Subject: [windbg] RE: Windbag not showing all the locals?
I’ve seen the same problem in unoptimized code w/ this build of the
debugger.
Seems to happen more with variables that are assigned in the same line
that they’re declared (e.g. “char *ptr = NULL” kind of things tend to
now show in the Locals window).
-----Original Message-----
From: Nathan Nesbit [mailto:xxxxx@windows.microsoft.com]
Sent: Monday, February 24, 2003 11:51 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: Windbag not showing all the locals?
If this is optimized code then some local variables may have been
optimized away…
-----Original Message-----
From: xxxxx@gcplc.com [mailto:xxxxx@gcplc.com]
Sent: Monday, February 24, 2003 11:06 AM
To: Kernel Debugging Interest List
Subject: [windbg] Windbag not showing all the locals?
I’m having a bit of a tear the hair out problem with windbg 6.1.0017.0
here. To be specific its not showing me all of the local variables
(makes the debugging a bit tricky). To be specific I am looking at a
full crash dump on W2K SP3 after PAGE_FAULT_IN_NON… and what I can see
is consistent with a garbage pointer dereference. Is there some
limitation is windbg here?
—
You are currently subscribed to windbg as: xxxxx@microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to windbg as: xxxxx@softek.fujitsu.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to windbg as: xxxxx@microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com
Somewhat embarassed. Its free build, so, yes, optimised.
Sometimes a .reload will clear it up also…
Doug
wrote in message news:xxxxx@windbg…
>
> I’m having a bit of a tear the hair out problem with windbg 6.1.0017.0
> here. To be specific its not showing me all of the local variables (makes
> the debugging a bit tricky). To be specific I am looking at a full crash
> dump on W2K SP3 after PAGE_FAULT_IN_NON… and what I can see is
> consistent with a garbage pointer dereference. Is there some limitation is
> windbg here?
>
>