Kernel Debugger (NT Driver Utility)

NTDEV
1

I was trying to build a “Kernel Debugger” for a Printer Driver (under
Windows NT ver.4.0).
Of course, before I would able to test my “Debugger” – I have to compile it
and link it to the
actual printer driver. Then execute the driver to see if my debugger does
its task. The problem
arises when I used I/O functions (such as ZwCreateFile, ZwWriteFile,
NtCreateFile, CloseHandle, etc.
especially C standard functions). Everytime I used such functions, the
printer driver itself
could not able to print/generate output. Is it really possible to use file
I/O functions when
designing a Kernel Debugger? If yes, why I encountered the said problem? –
is there any alternative
File I/O functions? If no, how could I possibly create a log file (since it
is a required output
of my Kernel Debugger).

  • Richard G. Villegas -

Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.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

2

Dear Guru;

My friends refer you to me. They said you are expert on this field.
Here is the scenario of mine:

I was trying to build a “Kernel Debugger” for a Printer Driver (under
Windows NT ver.4.0).
Of course, before I would able to test my “Debugger” – I have to compile it
and link it to the
actual printer driver. Then execute the driver to see if my debugger does
its task. The problem
arises when I used I/O functions (such as ZwCreateFile, ZwWriteFile,
NtCreateFile, CloseHandle, etc.
especially C standard functions). Everytime I used such functions, the
printer driver itself
could not able to print/generate output. Is it really possible to use file
I/O functions when
designing a Kernel Debugger? If yes, why I encountered the said problem? –
is there any alternative
File I/O functions? If no, how could I possibly create a log file (since it
is a required output
of my Kernel Debugger).

  • Richard G. Villegas -

Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.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

3

Hello:

I had gone through these kind of problems while writing a kernel mode
printer driver. It is just not possible to write to files from a NT 4.0
Kernel mode Printer Driver. All these zw calls would not work.

Try and see if you can write to a share memory for your logging. You can
then use another process to read from this memory.

Thank you,
RR

-----Original Message-----
From: Ricky Villegas [mailto:xxxxx@hotmail.com]
Sent: Thursday, February 01, 2001 12:02 PM
To: NT Developers Interest List
Subject: [ntdev] Kernel Debugger (NT Driver Utility)

Dear Guru;

My friends refer you to me. They said you are expert on this field.
Here is the scenario of mine:

I was trying to build a “Kernel Debugger” for a Printer Driver (under
Windows NT ver.4.0).
Of course, before I would able to test my “Debugger” – I have to compile it

and link it to the
actual printer driver. Then execute the driver to see if my debugger does
its task. The problem
arises when I used I/O functions (such as ZwCreateFile, ZwWriteFile,
NtCreateFile, CloseHandle, etc.
especially C standard functions). Everytime I used such functions, the
printer driver itself
could not able to print/generate output. Is it really possible to use file
I/O functions when
designing a Kernel Debugger? If yes, why I encountered the said problem? –
is there any alternative
File I/O functions? If no, how could I possibly create a log file (since it
is a required output
of my Kernel Debugger).

  • Richard G. Villegas -

Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

You are currently subscribed to ntdev as: xxxxx@ssdi.sharp.co.in
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

4

What do you mean, ‘build a “Kernel Debugger”’? Do you mean you are actually
trying to write your own debugger? Don’t do that, you obviously aren’t
experienced enough to do that. Use WinDBG, get it at
http://www.microsoft.com/ddk/debugging/. It will provide you with
everything you need (except knowledge) to debug your printer driver. To
find out how to output debug strings, do a search in the *DDK* documentation
for the word “print”.

-----Original Message-----
From: Ricky Villegas [mailto:xxxxx@hotmail.com]
Sent: Wednesday, January 31, 2001 10:29 PM
To: NT Developers Interest List
Subject: [ntdev] Kernel Debugger (NT Driver Utility)

I was trying to build a “Kernel Debugger” for a Printer Driver (under
Windows NT ver.4.0).
Of course, before I would able to test my “Debugger” – I have to compile it

and link it to the
actual printer driver. Then execute the driver to see if my debugger does
its task. The problem
arises when I used I/O functions (such as ZwCreateFile, ZwWriteFile,
NtCreateFile, CloseHandle, etc.
especially C standard functions). Everytime I used such functions, the
printer driver itself
could not able to print/generate output. Is it really possible to use file
I/O functions when
designing a Kernel Debugger? If yes, why I encountered the said problem? –
is there any alternative
File I/O functions? If no, how could I possibly create a log file (since it
is a required output
of my Kernel Debugger).

  • Richard G. Villegas -

Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

You are currently subscribed to ntdev as: xxxxx@intel.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