Thanks Nathan for your suggetions.
pls clear me some new problems.
Nathan >Use the version 3 beta rather than version
2.IMO the v3 betas are better than v2.
…now,i m using version 3 beta.
Nathan >Set the symbol path and do a .reload BEFORE
attempting to set breakpoints.
… yes,i executed .reload before attempting to
set breakpoint.
Nathan >Verify you that the symbols are loading
correctly. “!sym noisy”
…noisy mode is “ON” now,all the symbols are
loading correctly(no warning,no error after .reload)
when i set a breakpoint,and add a variable in watch
window it shows following message in command window
and display “cannot get any value” in watch window:->
"Module “ntoskrnl” was not found in the module list.
Debugger will attempt to load module “ntoskrnl” by
guessing the base address.
Please provide the full image name, including the
extension (i.e. kernel32.dll) for more reliable
results.
DBGHELP: FindExecutableImageEx-> Looking for
C:\Program Files\Debugging Tools for
Windows\ntoskrnl… no file
DBGHELP: FindExecutableImageEx-> Searching f:\test for
ntoskrnl… no file
DBGHELP: FindDebugInfoFileEx-> Looking for
f:\test\ntoskrnl.dbg… OK
DBGHELP: coff symbols loaded
*** WARNING: Unable to verify timestamp for ntoskrnl
DBGHELP: FindExecutableImageEx-> Searching f:\test for
ntoskrnlsym… no file
DBGHELP: FindDebugInfoFileEx-> Looking for
ntoskrnlsym.dbg… file not found
DBGHELP: diaLocatePDB-> Looking for ntoskrnlsym.pdb…
file not found
DBGHELP: no symbols loaded"
*******************************************************
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
******************************************************
here i haven’t writte other messages for which symbol
are loaded successfully.
how can i avoid this error?
Thanks
Akhil
— Nathan Nesbit
wrote: >
> When you see this message, “unable to retrieve the
> PEB address…” when
> you do a .reload it means that the user mode module
> list is paged out
> and therefore the debugger has no idea what modules
> to load symbols for
> at what addresses. This is true for UM modules
> only. So drivers are
> unaffected. The majority of the time when people
> are doing kernel
> debugging with Windbg they are interested in KM
> modules only and so this
> normally can be safely ignored.
>
> If you need to do user mode debugging and keep
> hitting this (and other
> paging issues) then you should really investigate
> using a user mode
> debugger (you can use windbg or cdb from the
> debugger package). Because
> the system is running when the UM debugger does a
> memory access, the
> memory will get paged in if it is not already.
>
> As to your breakpoint problem, here are some ideas:
> Use the version 3 beta rather than version 2. IMO
> the v3 betas
> are better than v2.
> Set the symbol path and do a .reload BEFORE
> attempting to set
> breakpoints.
> Verify you that the symbols are loading correctly.
> “!sym noisy”
> really helps to diagnose symbol problems.
>
____________________________________________________________
Do You Yahoo!?
For regular News updates go to http://in.news.yahoo.com
—
You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com