Provide more specific information. We can’t read your mind or your screen.
Attach a dump of the WinDbg/KD output and the commands you executed. It’s
the fastest way to figure out the problem, at least if you want help from
the list.
– arlie
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Albert Pinto
Sent: Tuesday, August 09, 2005 1:13 PM
To: Windows System Software Devs Interest List
Subject: SPAM-LOW: Re: SPAM-LOW: [ntdev] buffer problem
prokash,
It is just other way to look at to figure out if you happen to have
index problem when you are trying to print from the code.
I tried that, everything is fine, else it wouldn’t have gone into the
if…else i am using the same offset at both places and the condition
checker is hard coded!!!
no mistakes there
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
Are you running a chk build of your driver? If not, KdPrint goes away.
DbgPrint will always print out.
d
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Albert Pinto
Sent: Tuesday, August 09, 2005 10:13 AM
To: Windows System Software Devs Interest List
Subject: Re: SPAM-LOW: [ntdev] buffer problem
prokash,
It is just other way to look at to figure out if you happen to have
index
problem when you are trying to print from the code.
I tried that, everything is fine, else it wouldn’t have gone into the
if…else i am using the same offset at both places and the condition
checker is hard coded!!!
no mistakes there
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
It is always easy for us to shoot it down, if infos are properly given as
Arlie has been suggesting.
One other thing I would guess is that since you are using KdPrint, hope
you are using debug build. In otherwords DBG is defined. I’m only guessing
here and just to be sure that KdPrint is not getting translated to NOP due
to the macro definition.
-pro
Provide more specific information. We can’t read your mind or your
screen.
Attach a dump of the WinDbg/KD output and the commands you executed. It’s
the fastest way to figure out the problem, at least if you want help from
the list.
– arlie
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Albert Pinto
Sent: Tuesday, August 09, 2005 1:13 PM
To: Windows System Software Devs Interest List
Subject: SPAM-LOW: Re: SPAM-LOW: [ntdev] buffer problem
prokash,
>It is just other way to look at to figure out if you happen to have
>index problem when you are trying to print from the code.
I tried that, everything is fine, else it wouldn’t have gone into the
if…else i am using the same offset at both places and the condition
checker is hard coded!!!
no mistakes there
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@garlic.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
> if(buffer[OFFSET]==‘2’){
KdPrint((“\n 2 buffer[%u] is : %c”,OFFSET,buff[OFFSET]));
}
else if(buffer[OFFSET]==‘1’){
KdPrint((“\n 1 buffer[%u] is : %c”,OFFSET,buff[OFFSET]));
}
It sounds like the value at buffer[OFFSET} is neither ‘1’ or ‘2’, and this
code is working as written. You should add an else clause to the second if
that says something like:
else {
KdPrint((“\n buffer[%u] is not 1 or 2 but is : %c”,OFFSET,buff[OFFSET]));
}