Thank’s, Gary. I rest my case and peacefully accept it… Oh, and how
about those .dbg files? Do I need them? Isn’t the debug info already
placed in the .pdb?
BTW (off-topic), this reminds me of an old joke where there were 3 guys
(an electrician, a mechanic and a programmer) driving a car in a desert.
Suddenly, the car stops.
The electician saids: -There must be something wrong with the electric
system.
The mechanic saids: -Oh, no. Surely, the problem is mechanical.
Then the programmer saids: -Naah… Let us just leave the car and got
back inside!!
The old trick still works… exit and run it again, he?.. :)))
Miguel Monteiro
xxxxx@criticalsoftware.com
www.criticalsoftware.com
«Humour and love are God’s answers
to Human weaknesses»
On Tuesday, March 13, 2001 7:26 PM “Gary Little” wrote:
I think WinDbg needs a potty break very now and then.
I have gotten that also, as well as some really bogus symbols when I
have
been actively debugging across many many boots of the target. Reloading
WinDbg solves the problem for me.
Gary G. Little
Sr. Staff Engineer
Broadband Storage, LLC
xxxxx@broadstor.com
xxxxx@delphieng.com
-----Original Message-----
From: Miguel Monteiro [mailto:xxxxx@criticalsoftware.com]
Sent: Tuesday, March 13, 2001 10:59 AM
To: NT Developers Interest List
Subject: [ntdev] WinDbg quick tips
Hi there.
These two are quickies (I’m kind of new using WinDbg).
-
I’ve managed to get WinDbg working quite well. I’m developing a
kernel-mode driver
“prototype” and I’ve been using WinDbg (v2.0.0023.0) on a Host-Target
environment
running Win2K SP1. Everything seems to work fine, except that
*sometimes* (I say it
again: sometimes, not always) I get the below “annoying” message from
WinDbg. This may
sound stupid (perhaps it is, sorry), but I dunno why I’m getting it, as
everything else
(workspace, source/executable image/symbols loaded and the respective
paths) is set right.
I suspect it has something to do with recompiling my driver - which
doesn’t make great sense,
as I’m sure the proper .pdb file is there - or the *order* by which I
start a kernel-mode
debugging session (usually I start the driver first, then I break into
it, set breakpoints and
trace it from there). Does anyone have a clue of what’s going on? (BTW,
if I exit WinDbg, then
run WinDbg again and repeat the process, sometimes it starts working
again… ???) -
How do I create .dbg files? I’ve managed to get my drivers compiled
from VC (through
a batch file; this is great to locate errors on the source code), but
‘build’ simply creates the
“usual” .obj, .sys and .pdb files (and a .mac file, don’t ask me why).
I’ve managed to trace through
my driver code (both source and disassembly) and also through ntdll.dll.
So… do I *really* need
.dbg files? Isn’t the (debug) information already available in the .pdb
file?..
— The infamous “annoying” message from WinDbg… —
Loading User Symbols
Unable to retrieve the PEB address. This is usually caused
by being in the wrong process context or by paging
Module “MyDriver” was not found in the module list.
Debugger will attempt to load module “MyDriver” by guessing the base
address.
Please provide the full image name, including the extension (i.e.
kernel32.dll) for more reliable results.
************************************************************************
*
***
***
*** 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.
***
***
************************************************************************
*
This is weird, as:
kd> .sympath
Symbol search path is: C:\MyProjects\MyDriver\i386;C:\WINNT\Symbols
kd> .srcpath
Source search path is: C:\MyProjects\MyDriver
kd> .exepath
Executable image search path is: C:\MyProjects\MyDriver\i386
which is perfectly okay!.. Also, .reload works fine for the o.s.
symbols, but not .reload /user !..
I’m in the dark here… Any help would be great (these are easy for you
guys!..).
Miguel Monteiro
xxxxx@criticalsoftware.com
www.criticalsoftware.com
«Humour and love are God’s answers
to Human weaknesses»
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com