What VC settings can I use when building a driver to get a listing file from
which I can correlate the offset address displayed on a BSOD? When I create
listing files each module restarts the machine code address at zero - ???
I need it to start at zero and increment addresses all the way to the end of
the last module. Otherwise, I have to play calculator games which is a
drag.
Bill Casey
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
Never mind; answered my own question: MAP file!
Bill Casey
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
I’m assuming you also ran a link map? Sorry, but a good hex calculator is
invaluable for that kind of debunking. My trusty HP 16C has seen 2 sets of
batteries and is nearly worn out, after 14 years of use.
The listing setting I use is Assembly, Machine code, and Source
Gary G. Little
Sr. Staff Engineer
Broadband Storage, LLC
xxxxx@broadstor.com
xxxxx@delphieng.com
-----Original Message-----
From: Bill Casey [mailto:xxxxx@advstor.com]
Sent: Friday, March 02, 2001 1:26 PM
To: NT Developers Interest List
Subject: [ntdev] BSOD driver offset
What VC settings can I use when building a driver to get a listing file from
which I can correlate the offset address displayed on a BSOD? When I create
listing files each module restarts the machine code address at zero - ???
I need it to start at zero and increment addresses all the way to the end of
the last module. Otherwise, I have to play calculator games which is a
drag.
Bill Casey
You are currently subscribed to ntdev as: xxxxx@delphieng.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