Could anyone tell me how to produce a structure definition file so that I
can use the !strct command from the oem support tools with my own structures
and not just the nt native ones?
Thanks,
Todd J. Flanagan
Senior Developer
Gresham Enterprise Storage
xxxxx@openmic.com
(508)786-9656
Don’t bother. The new debuggers can extract your structure symbols from
your PDB files and display them exactly as !strct does, eliminating the need
for a structure definition file. Try the ‘dt’ command in the new debugger.
Mike Gilson
------Original Message------
From: “Todd Flanagan”
To: NT Developers Interest List
Sent: August 10, 2000 11:54:03 AM GMT
Subject: [ntdev] !strct in kdex2x86.dll
Could anyone tell me how to produce a structure definition file so that I
can use the !strct command from the oem support tools with my own structures
and not just the nt native ones?
Thanks,
Todd J. Flanagan
Senior Developer
Gresham Enterprise Storage
xxxxx@openmic.com
(508)786-9656
—
You are currently subscribed to ntdev as: xxxxx@gte.net
To unsubscribe send a blank email to $subst(‘Email.Unsub’)
There is a documentation file that will tell you how to use the kdex2x86
extensions. I’m assuming your using the Beta WinDbg, since it is the only
version of the debugger that is working. From the Start menu, select
Debugging Tools, OEM support tools, and lastly the word document titled OEM
tool Help. Using it, you can construct a usable INI file that the debugger
will load. However, it needs a lot of embellishment to define enums, bit
fields and unions. That tends to be trial and error.
Good luck!
-----Original Message-----
From: Todd Flanagan [mailto:xxxxx@mac.com]
Sent: Thursday, August 10, 2000 4:54 AM
To: NT Developers Interest List
Subject: [ntdev] !strct in kdex2x86.dll
Could anyone tell me how to produce a structure definition
file so that I
can use the !strct command from the oem support tools with
my own structures
and not just the nt native ones?
Thanks,
Todd J. Flanagan
Senior Developer
Gresham Enterprise Storage
xxxxx@openmic.com
(508)786-9656
You are currently subscribed to ntdev as:
xxxxx@delphieng.com
To unsubscribe send a blank email to
$subst(‘Email.Unsub’)
Michael,
I tried it. !dt dumps thread information, and is not documented in the !help
output. !dt -? Gives some nice information, however. I did do a dt -?
(without either a ! or a . bang prefix) and found the strct dump. Again dt
is not documented under help. Thanks!!!
Gary
-----Original Message-----
From: Michael Gilson [mailto:xxxxx@gte.net]
Sent: Thursday, August 10, 2000 6:23 AM
To: NT Developers Interest List
Subject: [ntdev] RE: !strct in kdex2x86.dll
Don’t bother. The new debuggers can extract your structure
symbols from
your PDB files and display them exactly as !strct does,
eliminating the need
for a structure definition file. Try the ‘dt’ command in
the new debugger.
Mike Gilson
------Original Message------
From: “Todd Flanagan”
To: NT Developers Interest List
Sent: August 10, 2000 11:54:03 AM GMT
Subject: [ntdev] !strct in kdex2x86.dll
Could anyone tell me how to produce a structure definition
file so that I
can use the !strct command from the oem support tools with
my own structures
and not just the nt native ones?
Thanks,
Todd J. Flanagan
Senior Developer
Gresham Enterprise Storage
xxxxx@openmic.com
(508)786-9656
—
You are currently subscribed to ntdev as: xxxxx@gte.net
To unsubscribe send a blank email to
$subst(‘Email.Unsub’)
—
You are currently subscribed to ntdev as:
xxxxx@delphieng.com
To unsubscribe send a blank email to
$subst(‘Email.Unsub’)
Not “!dt” just “dt” - see the help in the new windbg (and make sure you use
build 2250 which is the latest one available at the DDK web site)
Simon
-----Original Message-----
From: Gary Little [mailto:xxxxx@delphieng.com]
Sent: Thursday, August 10, 2000 11:46 AM
To: NT Developers Interest List
Subject: [ntdev] RE: !strct in kdex2x86.dll
Michael,
I tried it. !dt dumps thread information, and is not documented in the !help
output. !dt -? Gives some nice information, however. I did do a dt -?
(without either a ! or a . bang prefix) and found the strct dump. Again dt
is not documented under help. Thanks!!!
Gary
-----Original Message-----
From: Michael Gilson [mailto:xxxxx@gte.net]
Sent: Thursday, August 10, 2000 6:23 AM
To: NT Developers Interest List
Subject: [ntdev] RE: !strct in kdex2x86.dll
Don’t bother. The new debuggers can extract your structure
symbols from
your PDB files and display them exactly as !strct does,
eliminating the need
for a structure definition file. Try the ‘dt’ command in
the new debugger.
Mike Gilson
------Original Message------
From: “Todd Flanagan”
To: NT Developers Interest List
Sent: August 10, 2000 11:54:03 AM GMT
Subject: [ntdev] !strct in kdex2x86.dll
Could anyone tell me how to produce a structure definition
file so that I
can use the !strct command from the oem support tools with
my own structures
and not just the nt native ones?
Thanks,
Todd J. Flanagan
Senior Developer
Gresham Enterprise Storage
xxxxx@openmic.com
(508)786-9656
—
You are currently subscribed to ntdev as: xxxxx@gte.net
To unsubscribe send a blank email to
$subst(‘Email.Unsub’)
—
You are currently subscribed to ntdev as:
xxxxx@delphieng.com
To unsubscribe send a blank email to
$subst(‘Email.Unsub’)
—
You are currently subscribed to ntdev as: xxxxx@stratus.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)
Whatever … From what I have found the damn thing doesn’t work. Period.
I’ve tried this
dt IRP 808558e8
dt ntkrnlmp!IRP 808558e8
dt ntkrnlmp.dll!IRP 808558e8
I have no doubt that you got it to work, but I haven’t. So what’s the secret
(other than a large sledge hammer up side the head of the asshole that
didn’t document it!)
-----Original Message-----
From: Graham, Simon [mailto:xxxxx@stratus.com]
Sent: Thursday, August 10, 2000 9:17 AM
To: NT Developers Interest List
Subject: [ntdev] RE: !strct in kdex2x86.dll
Not “!dt” just “dt” - see the help in the new windbg (and
make sure you use
build 2250 which is the latest one available at the DDK web
site)
Simon
-----Original Message-----
From: Gary Little [mailto:xxxxx@delphieng.com]
Sent: Thursday, August 10, 2000 11:46 AM
To: NT Developers Interest List
Subject: [ntdev] RE: !strct in kdex2x86.dll
Michael,
I tried it. !dt dumps thread information, and is not
documented in the !help
output. !dt -? Gives some nice information, however. I did
do a dt -?
(without either a ! or a . bang prefix) and found the strct
dump. Again dt
is not documented under help. Thanks!!!
Gary
-----Original Message-----
From: Michael Gilson
[mailto:xxxxx@gte.net]
Sent: Thursday, August 10, 2000 6:23 AM
To: NT Developers Interest List
Subject: [ntdev] RE: !strct in
kdex2x86.dll
Don’t bother. The new debuggers can extract
your structure
symbols from
your PDB files and display them exactly as
!strct does,
eliminating the need
for a structure definition file. Try the
‘dt’ command in
the new debugger.
Mike Gilson
------Original Message------
From: “Todd Flanagan”
To: NT Developers Interest List
Sent: August 10, 2000 11:54:03 AM GMT
Subject: [ntdev] !strct in kdex2x86.dll
Could anyone tell me how to produce a
structure definition
file so that I
can use the !strct command from the oem
support tools with
my own structures
and not just the nt native ones?
Thanks,
Todd J. Flanagan
Senior Developer
Gresham Enterprise Storage
xxxxx@openmic.com
(508)786-9656
—
You are currently subscribed to ntdev as:
xxxxx@gte.net
To unsubscribe send a blank email to
$subst(‘Email.Unsub’)
—
You are currently subscribed to ntdev as:
xxxxx@delphieng.com
To unsubscribe send a blank email to
$subst(‘Email.Unsub’)
—
You are currently subscribed to ntdev as:
xxxxx@stratus.com
To unsubscribe send a blank email to
$subst(‘Email.Unsub’)
—
You are currently subscribed to ntdev as:
xxxxx@delphieng.com
To unsubscribe send a blank email to
$subst(‘Email.Unsub’)
Ok, as is the case, it appears I spoke out of turn. The secret is that you
can’t use the typedef, as you can with the kdex2x86 strct. So the proper
method of doing it is as follows:
dt _IRP 808558e8
And for my local structure:
dt anAdapterControl 808558e8
So smack me with the sledge.
-----Original Message-----
From: Gary Little [mailto:xxxxx@delphieng.com]
Sent: Thursday, August 10, 2000 5:07 PM
To: NT Developers Interest List
Subject: [ntdev] RE: !strct in kdex2x86.dll
Whatever … From what I have found the damn thing doesn’t
work. Period.
I’ve tried this
dt IRP 808558e8
dt ntkrnlmp!IRP 808558e8
dt ntkrnlmp.dll!IRP 808558e8
I have no doubt that you got it to work, but I haven’t. So
what’s the secret
(other than a large sledge hammer up side the head of the
asshole that
didn’t document it!)
-----Original Message-----
From: Graham, Simon
[mailto:xxxxx@stratus.com]
Sent: Thursday, August 10, 2000 9:17 AM
To: NT Developers Interest List
Subject: [ntdev] RE: !strct in
kdex2x86.dll
Not “!dt” just “dt” - see the help in the
new windbg (and
make sure you use
build 2250 which is the latest one available
at the DDK web
site)
Simon
-----Original Message-----
From: Gary Little
[mailto:xxxxx@delphieng.com]
Sent: Thursday, August 10, 2000 11:46 AM
To: NT Developers Interest List
Subject: [ntdev] RE: !strct in kdex2x86.dll
Michael,
I tried it. !dt dumps thread information,
and is not
documented in the !help
output. !dt -? Gives some nice information,
however. I did
do a dt -?
(without either a ! or a . bang prefix) and
found the strct
dump. Again dt
is not documented under help. Thanks!!!
Gary
-----Original Message-----
From: Michael Gilson
[mailto:xxxxx@gte.net]
Sent: Thursday, August 10,
2000 6:23 AM
To: NT Developers
Interest List
Subject: [ntdev] RE:
!strct in
kdex2x86.dll
Don’t bother. The new
debuggers can extract
your structure
symbols from
your PDB files and display
them exactly as
!strct does,
eliminating the need
for a structure definition
file. Try the
‘dt’ command in
the new debugger.
Mike Gilson
------Original Message------
From: “Todd Flanagan”
To: NT Developers Interest
List
Sent: August 10, 2000
11:54:03 AM GMT
Subject: [ntdev] !strct in
kdex2x86.dll
Could anyone tell me how to
produce a
structure definition
file so that I
can use the !strct command
from the oem
support tools with
my own structures
and not just the nt native
ones?
Thanks,
Todd J. Flanagan
Senior Developer
Gresham Enterprise Storage
xxxxx@openmic.com
(508)786-9656
—
You are currently subscribed
to ntdev as:
xxxxx@gte.net
To unsubscribe send a blank
email to
$subst(‘Email.Unsub’)
—
You are currently subscribed
to ntdev as:
xxxxx@delphieng.com
To unsubscribe send a blank
email to
$subst(‘Email.Unsub’)
—
You are currently subscribed to ntdev as:
xxxxx@stratus.com
To unsubscribe send a blank email to
$subst(‘Email.Unsub’)
—
You are currently subscribed to ntdev as:
xxxxx@delphieng.com
To unsubscribe send a blank email to
$subst(‘Email.Unsub’)
—
You are currently subscribed to ntdev as:
xxxxx@delphieng.com
To unsubscribe send a blank email to
$subst(‘Email.Unsub’)
Irritating isn’t it! Other things to note:
. the NT symbols are stripped of all the useful and interesting typedef
info,
so you can only use dt to dump types that are known by drivers with PDB
files (so
basically only publicly defined types from ntddk.h can be dumped - shame!)
. if you use a name with no driver name prefix, then it loads all of the
modules
until it finds one with a matching type. If you know a driver that has the
type
defined then its much faster to use “dt driver!type address”
. Use “-r1” to show embedded types; but this doesn’t work for arrays (yet;
hint hint)
. Use -v to see gory detail of type info (sometimes interesting for geeks
like me)
/simgr
-----Original Message-----
From: Gary Little [mailto:xxxxx@delphieng.com]
Sent: Thursday, August 10, 2000 8:33 PM
To: NT Developers Interest List
Subject: [ntdev] RE: !strct in kdex2x86.dll
Ok, as is the case, it appears I spoke out of turn. The secret is that you
can’t use the typedef, as you can with the kdex2x86 strct. So the proper
method of doing it is as follows:
dt _IRP 808558e8
And for my local structure:
dt anAdapterControl 808558e8
So smack me with the sledge.
-----Original Message-----
From: Gary Little [mailto:xxxxx@delphieng.com]
Sent: Thursday, August 10, 2000 5:07 PM
To: NT Developers Interest List
Subject: [ntdev] RE: !strct in kdex2x86.dll
Whatever … From what I have found the damn thing doesn’t
work. Period.
I’ve tried this
dt IRP 808558e8
dt ntkrnlmp!IRP 808558e8
dt ntkrnlmp.dll!IRP 808558e8
I have no doubt that you got it to work, but I haven’t. So
what’s the secret
(other than a large sledge hammer up side the head of the
asshole that
didn’t document it!)
-----Original Message-----
From: Graham, Simon
[mailto:xxxxx@stratus.com]
Sent: Thursday, August 10, 2000 9:17 AM
To: NT Developers Interest List
Subject: [ntdev] RE: !strct in
kdex2x86.dll
Not “!dt” just “dt” - see the help in the
new windbg (and
make sure you use
build 2250 which is the latest one available
at the DDK web
site)
Simon
-----Original Message-----
From: Gary Little
[mailto:xxxxx@delphieng.com]
Sent: Thursday, August 10, 2000 11:46 AM
To: NT Developers Interest List
Subject: [ntdev] RE: !strct in kdex2x86.dll
Michael,
I tried it. !dt dumps thread information,
and is not
documented in the !help
output. !dt -? Gives some nice information,
however. I did
do a dt -?
(without either a ! or a . bang prefix) and
found the strct
dump. Again dt
is not documented under help. Thanks!!!
Gary
-----Original Message-----
From: Michael Gilson
[mailto:xxxxx@gte.net]
Sent: Thursday, August 10,
2000 6:23 AM
To: NT Developers
Interest List
Subject: [ntdev] RE:
!strct in
kdex2x86.dll
Don’t bother. The new
debuggers can extract
your structure
symbols from
your PDB files and display
them exactly as
!strct does,
eliminating the need
for a structure definition
file. Try the
‘dt’ command in
the new debugger.
Mike Gilson
------Original Message------
From: “Todd Flanagan”
To: NT Developers Interest
List
Sent: August 10, 2000
11:54:03 AM GMT
Subject: [ntdev] !strct in
kdex2x86.dll
Could anyone tell me how to
produce a
structure definition
file so that I
can use the !strct command
from the oem
support tools with
my own structures
and not just the nt native
ones?
Thanks,
Todd J. Flanagan
Senior Developer
Gresham Enterprise Storage
xxxxx@openmic.com
(508)786-9656
—
You are currently subscribed
to ntdev as:
xxxxx@gte.net
To unsubscribe send a blank
email to
$subst(‘Email.Unsub’)
—
You are currently subscribed
to ntdev as:
xxxxx@delphieng.com
To unsubscribe send a blank
email to
$subst(‘Email.Unsub’)
—
You are currently subscribed to ntdev as:
xxxxx@stratus.com
To unsubscribe send a blank email to
$subst(‘Email.Unsub’)
—
You are currently subscribed to ntdev as:
xxxxx@delphieng.com
To unsubscribe send a blank email to
$subst(‘Email.Unsub’)
—
You are currently subscribed to ntdev as:
xxxxx@delphieng.com
To unsubscribe send a blank email to
$subst(‘Email.Unsub’)
—
You are currently subscribed to ntdev as: xxxxx@stratus.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)
Well, it is only BETA, after all. (My my how mild I am after a good nights
sleep!!) But if Nathan is reading, and really wants to make WinDbg easier to
use …
-----Original Message-----
From: Graham, Simon [mailto:xxxxx@stratus.com]
Sent: Thursday, August 10, 2000 6:48 PM
To: NT Developers Interest List
Subject: [ntdev] RE: !strct in kdex2x86.dll
Irritating isn’t it! Other things to note:
. the NT symbols are stripped of all the useful and
interesting typedef
info,
so you can only use dt to dump types that are known by
drivers with PDB
files (so
basically only publicly defined types from ntddk.h can be
dumped - shame!)
. if you use a name with no driver name prefix, then it
loads all of the
modules
until it finds one with a matching type. If you know a
driver that has the
type
defined then its much faster to use “dt driver!type
address”
. Use “-r1” to show embedded types; but this doesn’t work
for arrays (yet;
hint hint)
. Use -v to see gory detail of type info (sometimes
interesting for geeks
like me)
/simgr
-----Original Message-----
From: Gary Little [mailto:xxxxx@delphieng.com]
Sent: Thursday, August 10, 2000 8:33 PM
To: NT Developers Interest List
Subject: [ntdev] RE: !strct in kdex2x86.dll
Ok, as is the case, it appears I spoke out of turn. The
secret is that you
can’t use the typedef, as you can with the kdex2x86 strct.
So the proper
method of doing it is as follows:
dt _IRP 808558e8
And for my local structure:
dt anAdapterControl 808558e8
So smack me with the sledge.
-----Original Message-----
From: Gary Little
[mailto:xxxxx@delphieng.com]
Sent: Thursday, August 10, 2000 5:07 PM
To: NT Developers Interest List
Subject: [ntdev] RE: !strct in
kdex2x86.dll
Whatever … From what I have found the
damn thing doesn’t
work. Period.
I’ve tried this
dt IRP 808558e8
dt ntkrnlmp!IRP 808558e8
dt ntkrnlmp.dll!IRP 808558e8
I have no doubt that you got it to work, but
I haven’t. So
what’s the secret
(other than a large sledge hammer up side
the head of the
asshole that
didn’t document it!)
-----Original Message-----
From: Graham, Simon
[mailto:xxxxx@stratus.com]
Sent: Thursday, August 10,
2000 9:17 AM
To: NT Developers
Interest List
Subject: [ntdev] RE:
!strct in
kdex2x86.dll
Not “!dt” just “dt” - see
the help in the
new windbg (and
make sure you use
build 2250 which is the
latest one available
at the DDK web
site)
Simon
-----Original Message-----
From: Gary Little
[mailto:xxxxx@delphieng.com]
Sent: Thursday, August 10,
2000 11:46 AM
To: NT Developers Interest
List
Subject: [ntdev] RE: !strct
in kdex2x86.dll
Michael,
I tried it. !dt dumps thread
information,
and is not
documented in the !help
output. !dt -? Gives some
nice information,
however. I did
do a dt -?
(without either a ! or a .
bang prefix) and
found the strct
dump. Again dt
is not documented under
help. Thanks!!!
Gary
-----Original Message-----
From:
Michael Gilson
[mailto:xxxxx@gte.net]
Sent:
Thursday, August 10,
2000 6:23 AM
To: NT
Developers
Interest List
Subject:
[ntdev] RE:
!strct in
kdex2x86.dll
Don’t
bother. The new
debuggers can extract
your structure
symbols from
your PDB
files and display
them exactly as
!strct does,
eliminating the need
for a
structure definition
file. Try the
‘dt’ command in
the new debugger.
Mike Gilson
------Original Message------
From: “Todd
Flanagan”
To: NT
Developers Interest
List
Sent: August
10, 2000
11:54:03 AM GMT
Subject:
[ntdev] !strct in
kdex2x86.dll
Could anyone
tell me how to
produce a
structure definition
file so that I
can use the
!strct command
from the oem
support tools with
my own structures
and not just
the nt native
ones?
Thanks,
Todd J.
Flanagan
Senior
Developer
Gresham
Enterprise Storage
xxxxx@openmic.com
(508)786-9656
—
You are
currently subscribed
to ntdev as:
xxxxx@gte.net
To
unsubscribe send a blank
email to
$subst(‘Email.Unsub’)
—
You are
currently subscribed
to ntdev as:
xxxxx@delphieng.com
To
unsubscribe send a blank
email to
$subst(‘Email.Unsub’)
—
You are currently subscribed
to ntdev as:
xxxxx@stratus.com
To unsubscribe send a blank
email to
$subst(‘Email.Unsub’)
—
You are currently subscribed
to ntdev as:
xxxxx@delphieng.com
To unsubscribe send a blank
email to
$subst(‘Email.Unsub’)
—
You are currently subscribed to ntdev as:
xxxxx@delphieng.com
To unsubscribe send a blank email to
$subst(‘Email.Unsub’)
—
You are currently subscribed to ntdev as:
xxxxx@stratus.com
To unsubscribe send a blank email to
$subst(‘Email.Unsub’)
—
You are currently subscribed to ntdev as:
xxxxx@delphieng.com
To unsubscribe send a blank email to
$subst(‘Email.Unsub’)