Hi!
I am new to driver development and am just feeling
my way around WinDebug. I have a problem.
I am not able to view the local variables in the
Locals window. I don’t get anything in the Watch
window either. Whenever I type in something, I get a
string of asterics and ‘could not resolve symbol’ in
the next line.
- I am NOT using the Checked build on the target
system. I don’t have it.
- I think that the symbols are loading correctly,
cause, I don’t get any errors or warnings.
- I have tried stripping the ‘.sys’ file of the
debug symbols and putting the ‘.dbg’ file in the
symbols folder.
Can anyone tell me what I am doing wrong. I should
be able to view the variables, shouldn’t I?
Thanks in advance!
Manoj
Do You Yahoo!?
Everything you’ll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com
You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
This could be several things.
- Make sure you are using the lastest windbg from
http://www.microsoft.com/ddk/debugging
- Make sure correct symbols are being loaded. Noisy symbol
loading helps with this. Type “!sym noisy” at the command prompt or add
“-n” to the command line used to start windbg.
- Make sure you are using PDB files. Windbg only supports
locals for PDB symbol types (this sounds like your problem).
- If the code is being optimized this some locals may be
optimized away and not appear. Other locals that appear may have
incorrect values. This is a limitation of the symbol file format in
describing what the compiler did. So debug unoptimized code if you can.
-----Original Message-----
From: Manoj Paul Joseph [mailto:xxxxx@yahoo.com]
Sent: Monday, January 14, 2002 8:52 PM
To: File Systems Developers
Subject: [ntfsd] WinDebug - Watch and Locals windows…
Hi!
I am new to driver development and am just feeling
my way around WinDebug. I have a problem.
I am not able to view the local variables in the
Locals window. I don’t get anything in the Watch
window either. Whenever I type in something, I get a
string of asterics and ‘could not resolve symbol’ in
the next line.
- I am NOT using the Checked build on the target
system. I don’t have it.
- I think that the symbols are loading correctly,
cause, I don’t get any errors or warnings.
- I have tried stripping the ‘.sys’ file of the
debug symbols and putting the ‘.dbg’ file in the
symbols folder.
Can anyone tell me what I am doing wrong. I should
be able to view the variables, shouldn’t I?
Thanks in advance!
Manoj
Do You Yahoo!?
Everything you’ll ever need on one web page
from News and Sport to Email and Music Charts http://uk.my.yahoo.com
You are currently subscribed to ntfsd as: xxxxx@microsoft.com To
unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Hi Nathan!
When I strip the .sys file of the debug symbols, I
end up with a ‘.dbg’ file. How do I get a ‘.pdb’ file?
Please explain.
Manoj
-----Original Message-----
“Nathan Nesbit” Wrote
This could be several things.
- Make sure you are using the lastest windbg from
http://www.microsoft.com/ddk/debugging
- Make sure correct symbols are being loaded. Noisy
symbol
loading helps with this. Type “!sym noisy” at the
command prompt or
add
“-n” to the command line used to start windbg.
- Make sure you are using PDB files. Windbg only
supports
locals for PDB symbol types (this sounds like your
problem).
- If the code is being optimized this some locals
may be
optimized away and not appear. Other locals that
appear may have
incorrect values. This is a limitation of the symbol
file format in
describing what the compiler did. So debug
unoptimized code if you
can.
-----Original Message-----
From: Manoj Paul Joseph
[mailto:xxxxx@yahoo.com]
Sent: Monday, January 14, 2002 8:52 PM
To: File Systems Developers
Subject: [ntfsd] WinDebug - Watch and Locals
windows…
Hi!
I am new to driver development and am just feeling
my way around WinDebug. I have a problem.
I am not able to view the local variables in the
Locals window. I don’t get anything in the Watch
window either. Whenever I type in something, I get a
string of asterics and ‘could not resolve symbol’ in
the next line.
- I am NOT using the Checked build on the target
system. I don’t have it.
- I think that the symbols are loading correctly,
cause, I don’t get any errors or warnings.
- I have tried stripping the ‘.sys’ file of the
debug symbols and putting the ‘.dbg’ file in the
symbols folder.
Can anyone tell me what I am doing wrong. I should
be able to view the variables, shouldn’t I?
Thanks in advance!
Manoj
Do You Yahoo!?
Everything you’ll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com
You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Hi Nathan!
When I strip the .sys file of the debug symbols, I end up with a ‘.dbg’ file. How do I get a ‘.pdb’ file? Please explain.
Manoj
-----Original Message-----
“Nathan Nesbit” Wrote
This could be several things.
- Make sure you are using the lastest windbg from
http://www.microsoft.com/ddk/debugging
- Make sure correct symbols are being loaded. Noisy symbol
loading helps with this. Type “!sym noisy” at the command prompt or
add
“-n” to the command line used to start windbg.
- Make sure you are using PDB files. Windbg only supports
locals for PDB symbol types (this sounds like your problem).
- If the code is being optimized this some locals may be
optimized away and not appear. Other locals that appear may have
incorrect values. This is a limitation of the symbol file format in
describing what the compiler did. So debug unoptimized code if you
can.
-----Original Message-----
From: Manoj Paul Joseph [mailto:xxxxx@yahoo.com]
Sent: Monday, January 14, 2002 8:52 PM
To: File Systems Developers
Subject: [ntfsd] WinDebug - Watch and Locals windows…
Hi!
I am new to driver development and am just feeling
my way around WinDebug. I have a problem.
I am not able to view the local variables in the
Locals window. I don’t get anything in the Watch
window either. Whenever I type in something, I get a
string of asterics and ‘could not resolve symbol’ in
the next line.
- I am NOT using the Checked build on the target
system. I don’t have it.
- I think that the symbols are loading correctly,
cause, I don’t get any errors or warnings.
- I have tried stripping the ‘.sys’ file of the
debug symbols and putting the ‘.dbg’ file in the
symbols folder.
Can anyone tell me what I am doing wrong. I should
be able to view the variables, shouldn’t I?
Thanks in advance!
Manoj
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
By compiling with the right options. VC6’s options are /PDB to link, and /Zi to the compiler.
Andy.
-----Original Message-----
From: Manoj Paul Joseph [mailto:xxxxx@yahoo.com]
Sent: 15 January 2002 05:30
To: File Systems Developers
Subject: [ntfsd] RE: WinDebug - Watch and Locals windows…
Hi Nathan!
When I strip the .sys file of the debug symbols, I
end up with a ‘.dbg’ file. How do I get a ‘.pdb’ file?
Please explain.
Manoj
–
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup
1 cent a minute calls anywhere in the U.S.!
http://www.getpennytalk.com/cgi-bin/adforward.cgi?p_key=RG9853KJ&url=http://www.getpennytalk.com
You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
The ddk/ifs kit build environment should supply the correct compiler and
linker automatically.
-----Original Message-----
From: Andy Champ [mailto:xxxxx@earthling.net]
Sent: Tuesday, January 15, 2002 12:57 AM
To: File Systems Developers
Subject: [ntfsd] RE: WinDebug - Watch and Locals windows…
By compiling with the right options. VC6’s options are /PDB to link, and
/Zi to the compiler.
Andy.
-----Original Message-----
From: Manoj Paul Joseph [mailto:xxxxx@yahoo.com]
Sent: 15 January 2002 05:30
To: File Systems Developers
Subject: [ntfsd] RE: WinDebug - Watch and Locals windows…
Hi Nathan!
When I strip the .sys file of the debug symbols, I
end up with a ‘.dbg’ file. How do I get a ‘.pdb’ file?
Please explain.
Manoj
–
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup
1 cent a minute calls anywhere in the U.S.!
http://www.getpennytalk.com/cgi-bin/adforward.cgi?p_key=RG9853KJ&url=http://
www.getpennytalk.com
You are currently subscribed to ntfsd as: xxxxx@congruent.com
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Put
USE_PDB=1
in SOURCES file.
Max
----- Original Message -----
From: “Manoj Paul Joseph”
To: “File Systems Developers”
Sent: Tuesday, January 15, 2002 8:29 AM
Subject: [ntfsd] RE: WinDebug - Watch and Locals windows…
> Hi Nathan!
> When I strip the .sys file of the debug symbols, I
> end up with a ‘.dbg’ file. How do I get a ‘.pdb’ file?
> Please explain.
> Manoj
>
> -----Original Message-----
> “Nathan Nesbit” Wrote
> This could be several things.
>
> 1) Make sure you are using the lastest windbg from
> http://www.microsoft.com/ddk/debugging
> 2) Make sure correct symbols are being loaded. Noisy
> symbol
> loading helps with this. Type “!sym noisy” at the
> command prompt or
> add
> “-n” to the command line used to start windbg.
> 3) Make sure you are using PDB files. Windbg only
> supports
> locals for PDB symbol types (this sounds like your
> problem).
> 4) If the code is being optimized this some locals
> may be
> optimized away and not appear. Other locals that
> appear may have
> incorrect values. This is a limitation of the symbol
> file format in
> describing what the compiler did. So debug
> unoptimized code if you
> can.
>
> -----Original Message-----
> From: Manoj Paul Joseph
> [mailto:xxxxx@yahoo.com]
> Sent: Monday, January 14, 2002 8:52 PM
> To: File Systems Developers
> Subject: [ntfsd] WinDebug - Watch and Locals
> windows…
>
>
> Hi!
> I am new to driver development and am just feeling
> my way around WinDebug. I have a problem.
> I am not able to view the local variables in the
> Locals window. I don’t get anything in the Watch
> window either. Whenever I type in something, I get a
> string of asterics and ‘could not resolve symbol’ in
> the next line.
> 1. I am NOT using the Checked build on the target
> system. I don’t have it.
> 2. I think that the symbols are loading correctly,
> cause, I don’t get any errors or warnings.
> 3. I have tried stripping the ‘.sys’ file of the
> debug symbols and putting the ‘.dbg’ file in the
> symbols folder.
> Can anyone tell me what I am doing wrong. I should
> be able to view the variables, shouldn’t I?
> Thanks in advance!
> Manoj
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Everything you’ll ever need on one web page
> from News and Sport to Email and Music Charts
> http://uk.my.yahoo.com
>
> —
> You are currently subscribed to ntfsd as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
—
You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com