I realize this question is not quite related to Driver development, but it is somewhat related to WinDbg. I really like how WinDbg can display the type information with symbols contained in the pdb.
Is there a way to display this without actually running the binary? Suppose, for example, that I have a DLL. Short of running the code inside of dllmain, is there a way I can display the types contained within?
You can use either dia2dump (Visual Studio) or dbh (windbg) to operate on
the pdb/exe directly. I’m not sure that either of have documentation, but
both come with source code.
Good luck,
mm
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@yahoo.com
Sent: Wednesday, September 08, 2010 5:10 PM
To: Kernel Debugging Interest List
Subject: [windbg] Displaying type information without running code
I realize this question is not quite related to Driver development, but it
is somewhat related to WinDbg. I really like how WinDbg can display the
type information with symbols contained in the pdb.
Is there a way to display this without actually running the binary?
Suppose, for example, that I have a DLL. Short of running the code inside
of dllmain, is there a way I can display the types contained within?
“M. M. O’Brien” wrote in message news:xxxxx@windbg… > You can use either dia2dump (Visual Studio) or dbh (windbg) to operate on > the pdb/exe directly. I’m not sure that either of have documentation, but > both come with source code. > > > Good luck, > > mm > > -----Original Message----- > From: xxxxx@lists.osr.com > [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@yahoo.com > Sent: Wednesday, September 08, 2010 5:10 PM > To: Kernel Debugging Interest List > Subject: [windbg] Displaying type information without running code > > I realize this question is not quite related to Driver development, but it > is somewhat related to WinDbg. I really like how WinDbg can display the > type information with symbols contained in the pdb. > > Is there a way to display this without actually running the binary? > Suppose, for example, that I have a DLL. Short of running the code inside > of dllmain, is there a way I can display the types contained within? > > > > — > WINDBG is sponsored by OSR > > For our schedule of WDF, WDM, debugging and other seminars visit: > http://www.osr.com/seminars > > To unsubscribe, visit the List Server section of OSR Online at > http://www.osronline.com/page.cfm?name=ListServer > >
Depending on what you are trying to do, this is probably a better idea.
mm
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
Sent: Wednesday, September 08, 2010 9:55 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Displaying type information without running code
You can also open the image as a dump file and use the dt command as normal.
“M. M. O’Brien” wrote in message news:xxxxx@windbg… > You can use either dia2dump (Visual Studio) or dbh (windbg) to operate on > the pdb/exe directly. I’m not sure that either of have documentation, but > both come with source code. > > > Good luck, > > mm > > -----Original Message----- > From: xxxxx@lists.osr.com > [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@yahoo.com > Sent: Wednesday, September 08, 2010 5:10 PM > To: Kernel Debugging Interest List > Subject: [windbg] Displaying type information without running code > > I realize this question is not quite related to Driver development, but it > is somewhat related to WinDbg. I really like how WinDbg can display the > type information with symbols contained in the pdb. > > Is there a way to display this without actually running the binary? > Suppose, for example, that I have a DLL. Short of running the code inside > of dllmain, is there a way I can display the types contained within? > > > > — > WINDBG is sponsored by OSR > > For our schedule of WDF, WDM, debugging and other seminars visit: > http://www.osr.com/seminars > > To unsubscribe, visit the List Server section of OSR Online at > http://www.osronline.com/page.cfm?name=ListServer > >