…and now for a painfully naive question…
Coming from the world of application development (and being rather
new to that, as well) I’ve had little reason or opportunity to ‘disassemble’
code. I have only a passing familiarity with assembler. Sure, occasionally
I’ve needed to step through some dissembled code while debugging, mostly
relying on symbols to keep my bearing, but I’ve never done what you
describe, Maxim. How do you go about doing this sort of thing? In my
naivety, I can imagine stepping into the routine with the debugger and
copying the disassembly into a file, then running it through an assembler
and eventually linking it into my project. Is this what you mean?
In the preface to Inside Windows 2000 David Solomon talks about how
impressed he is about how his co -author Mark Russinovich(sp?) can quickly
research issues by stepping though his ‘custom disassembled kernel’. Ever
since I’ve been wondering if it is common practice for the gurus of the
world to disassemble large binaries and debug them conventionally. If so,
what are some popular ‘disassemblers’?
Thanks,
-Joel
-----Original Message-----
From: Maxim S. Shatskih [mailto:xxxxx@storagecraft.com]
Sent: Wednesday, December 20, 2000 12:07 PM
To: File Systems Developers
Subject: [ntfsd] Re: NT4+IoCancelFileOpen
Anybody knows how to solve this: I’m use IoCancelFileOpen in my code and
also wants to build NT4 version of driver on my Win2k machine, but in the
NT4 DDK there is no such function in headers/libraries. I’m declare
Disassemble it, restore the source and write your own IoCancelFileOpen on
NT4. It is rather small - it just sends CLEANUP and CLOSE IRPs.
Max
You are currently subscribed to ntfsd as: xxxxx@ntpsoftware.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