The tools boil down to an API, and code must be written to negotiate the
API. Takes time and effort. And it’s easier to support pdb formats in the
symbol loader, that’s just an app, than in SoftICE, that’s a big and complex
piece of kernel code. Like Java bytecode, NMS insulates SoftICE from app
level changes.
Alberto.
-----Original Message-----
From: Gary Little [mailto:xxxxx@Broadstor.com]
Sent: Monday, October 15, 2001 6:03 PM
To: NT Developers Interest List
Subject: [ntdev] RE: How can I debug my driver at source-level with So
ftICE?
Oooohhhh … so the PDB is accessible with the proper tools? Then why doesn’t
NuMega have, and or use those tools? The PDB files are released with each
build, and thus available at the time of release. If SoftIce utilized the
PDB files then they just might avoid the build/release symbol problem that
periodically hinders the product for use in debugging drivers during a beta
cycle. Supporting the PDB and NMS makes a lot since. Why doesn’t SoftIce
provide that support? Supporting only NMS is a bit arrogant, and obviously
foolish.
Sorry, regardless of the strength of the NMS files they still have a very
large weakness … Numega must work some NuMega magic to support all builds
of a Windows OS.
Gary G. Little
Staff Engineer
Broadband Storage, Inc.
xxxxx@broadstor.com
-----Original Message-----
From: Michal Vodicka [mailto:xxxxx@veridicom.cz.nospam]
Sent: Monday, October 15, 2001 12:27 PM
To: NT Developers Interest List
Subject: [ntdev] RE: How can I debug my driver at source-level with So
ftICE?
From: Gary Little[SMTP:xxxxx@Broadstor.com]
Reply To: NT Developers Interest List
Sent: Monday, October 15, 2001 7:17 PM
To: NT Developers Interest List
Subject: [ntdev] RE: How can I debug my driver at source-level with
So ftICE?My only need is a development/debugger system that works with any release
of
Windows. Perhaps the biggest problem with SoftIce is that it insists on
using NMS files instead of the PDB files that are generated by the
compiler/linker?
If they were able to access debug info in new PDB files, there would be no
problem converting them to NMS. To access PDB info, you need a m$ DLL which
is able to do it. Personally, I prefer NMS way because sources can be
packaged with symbols and the NMS file is the only thing necessary for
source debugging. It helps when a crash occur on another computer. Also, I
save NMS files with all binaries so have no problem debugging an old version
which causes problem for a customer (no need to restore source tree from
VCS).
Gary, I can understand you can’t resist but is it really necessary to start
the windbg versus softice discussion again and again?
Best regards,
Michal Vodicka
Veridicom
(RKK - Skytale)
[WWW: http://www.veridicom.com , http://www.skytale.com]
You are currently subscribed to ntdev as: xxxxx@broadstor.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: xxxxx@compuware.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
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