difference between devstudio build and ddkbuild of user code

[netskink]

Hello

I have a driver, user library and user level unit test code. I used
to have identical behaviour when I built the user level code with
devstudio or the ddk/sdk. I even had the same behaviour when I built
the code using the ddk but the devstudio tools/libs. Now, I have a
difference. I am not sure what has changed, but I map memory and the
do writes to it. If I read back what I wrote using the ddk build, I
get all F's or all zero's. If I use the devstudio build I read what I
wrote.

I have tried to compare the compiler settings and I can not find a
difference other than small things such as /Mdd, /EHsc /RTC1 or /GM.
These settings are present in working version built by devstudio.
They are missing in the ddk version.

Any advice or tips to solve this is much appreciated.

John

[4***@email.com]

 If I read back what I wrote using the ddk build, I get all
F's or all zero's.  If I use the devstudio build I read what I wrote.

visual studio is preferred since historically it has produced good
code release after release. The compiler shipped in the ddk
historically has been unreliable with numerous compiler bugs and is
also usually back a generation as far as features and optimization is
concerned.

[netskink]

Post by 4***@email.com

 If I read back what I wrote using the ddk build, I get all
F's or all zero's.  If I use the devstudio build I read what I wrote.

visual studio is preferred since historically it has produced good
code release after release. The compiler shipped in the ddk
historically has been unreliable with numerous compiler bugs and is
also usually back a generation as far as features and optimization is
concerned.

Ok. Thanks. I'll just let it go then.

[netskink]

Post by 4***@email.com

 If I read back what I wrote using the ddk build, I get all
F's or all zero's.  If I use the devstudio build I read what I wrote.

visual studio is preferred since historically it has produced good
code release after release. The compiler shipped in the ddk
historically has been unreliable with numerous compiler bugs and is
also usually back a generation as far as features and optimization is
concerned.

I was thinking of another approach. Is it possible to compare two
binaries with some tool to see what some sort of global differences?

[4***@email.com]

Is it possible to compare two binaries with some tool to see what some sort of global differences?

Pass the command line parameter to have the compilers generate an
assembly output file and compare the two.