Hello everyone,
In my driver, I’m facing a strange problem while printing contents of
memory contents of pci device. Its printing “FFFFFFF”.
The memory is mapped into system using Haltranslatebusaddress and
followed by MMmapiospace. Till I call HalSetBusDataOffset the contents
are valid in memory.
Interestingly If I use DbgPrint to print a message, the contents of
memory are valid.
Please suggest me how to solve this problem.
Thanks
I’m guessing that you’re using a local variable to store the buffer used by
HalSetBusDataByOffset and your buffer either isn’t the right size or is
declared as the size of a pointer to the structure rather than the size of
the structure itself.
Almost every time I’ve had a problem that was fixed by putting in a
DbgPrint, the root of the problem was that I was misusing my stack space.
–
Jake Oshins
Windows Base Kernel Team
This posting is provided “AS IS” with no warranties, and confers no rights.
OR if you wish to include a script sample in your post please add “Use of
included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm”
“kupendra” wrote in message news:xxxxx@ntdev…
>
> Hello everyone,
>
> In my driver, I’m facing a strange problem while printing contents of
> memory contents of pci device. Its printing “FFFFFFF”.
>
> The memory is mapped into system using Haltranslatebusaddress and
> followed by MMmapiospace. Till I call HalSetBusDataOffset the contents
> are valid in memory.
>
> Interestingly If I use DbgPrint to print a message, the contents of
> memory are valid.
>
> Please suggest me how to solve this problem.
>
> Thanks
>
>