Re: Build device driver using Microsoft Visual C++ 2005

If its true that SoftIce has been flushed then driver development just got
ten times harder ... from now until the end of time ... or until it gets
un-flushed or MS update WinDbg so that you can debug on the host from the
host.

"David J. Craig" wrote:

Maybe he could call Compuware and ask when the new PDB format will be
supported. Never, since SoftIce has been flushed.

"Gary G. Little" <gary.g.little@xxxxxxxxxxx> wrote in message
news:44858cf9$0$15784$88260bb3@xxxxxxxxxxxxxxxxxxxxxxxx
I did, and replied, and the answer still holds ... DON'T. By and large, it
is a waste of time for the entire universe of answers that have already
been thrown at every excuse imaginable for such a dumb idea as using
anything other than the DDK compiler to build a driver. Note, I did not
call you dumb, so don't come back all indignant, I said your idea is dumb,
and we all have dumb ideas now and then.

The biggest reason for avoiding the VS compiler is quite readily seen when
you compare the VS compiler to the DDK compiler. The current DDK compiler
is at rev 13, whereas the VS compiler is at rev 14. Obvioulsy the two
compilers are different. What, or how they differ, I have no idea, but one
thing is for sure, I DON'T want to waste time and money chasing down a bug
simply to findout it's because I'm using the wrong compiler.

Microsoft does not support drivers compiled with anything other than the
compiler in the DDK. If I want Microsoft support I have to build with the
DDK compiler. To do anything else is, I am sorry, dumb. Therefore, I could
care less about the difference in your 2005 PDB files. Use BUILD, or
DDKBUILD, on your driver and then come back and talk about PDB files.

--
The personal opinion of
Gary G. Little

"mirage2k2" <mirage2k2@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:665D1F74-2BCC-4F1C-B41B-8338CED21FEF@xxxxxxxxxxxxxxxx
Gary, please see my new post "Building a device driver using VC6 and
VC2005"

I AM building the driver using VC2005 and its fine ... just that there is
something different about the pdb file that is generated. The new pdb is
larger so I doubt that it contains any less symbolic information than the
old
one and I have configured my project up to the hilt ... to generate as
much
debug data as possible.

There must be something different about the new pdb because, 1) older
version of WinDbg cannot get all symbols out of the pdb, 2) SoftIce
symbol
loader cannot get all symbols out of the pdb.

MS please help!

"Gary G. Little" wrote:

You say you are building your driver with VS 2005, but precisely how are
you
doing that? Are you using VS to edit and maintain you sources and
projects,
and then either using DDKBUILD or a DDK command line environment to
actually
build your driver? Or are you really invoking an IDE build and using the
VS
compilers? If the latter ... DON'T ... it's the wrong compiler to be
using
for device drivers.

Now, having said that, to generate PDB files, all you need to do is
invoke a
checked build environment and run BLD or BUILD -cze, or your switches of
choice, or use DDKBUILD from a VS makefile project.

--
The personal opinion of
Gary G. Little

"mirage2k2" <mirage2k2@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E74AE9F6-9D92-4313-B268-AD3484C8112F@xxxxxxxxxxxxxxxx
I've just started building my driver using Microsoft Visual C++ 2005.
I
notice the .pdb generated by the newer compiler/linker is different to
the
one v6 generated. For a start I had to upgrade WinDbg to the latest
version
in order for it to correctly get all symbols from the .pdb. Now I
have
problems with softice ... it too has trouble with the newer .pdb.

Does anyone know what has changed with respect to .pdb? Does anyone
know
how to get the new compiler/linker to output a .pdb like v6 did?









.

Relevant Pages

  • Re: Build device driver using Microsoft Visual C++ 2005
    ... other than the DDK compiler to build a driver. ... you compare the VS compiler to the DDK compiler. ... on your driver and then come back and talk about PDB files. ...
    (microsoft.public.development.device.drivers)
  • Re: Build device driver using Microsoft Visual C++ 2005
    ... Maybe he could call Compuware and ask when the new PDB format will be ... anything other than the DDK compiler to build a driver. ... on your driver and then come back and talk about PDB files. ...
    (microsoft.public.development.device.drivers)
  • lucent modem driver compilation failure
    ... I'm trying to compile an installable module for my internal modem ... and driver work as they were fully functional under RH7.3. ... 00:07.2 USB Controller: VIA Technologies, ... If not present use the ltmodem-8.22a5.tar.gz compiler kit. ...
    (linux.redhat.misc)
  • lucent modem driver compilation failure
    ... I'm trying to compile an installable module for my internal modem ... and driver work as they were fully functional under RH7.3. ... 00:07.2 USB Controller: VIA Technologies, ... If not present use the ltmodem-8.22a5.tar.gz compiler kit. ...
    (comp.os.linux.hardware)
  • Re: Microfocus Netexpress question : COBSQL vs openESQL
    ... >couldnt connect with the oracle database specified in the program. ... It may be missing an ODBC driver and/or data source. ... You also need an entry for the data source in tnsnames.ora. ... precompiler directives to the precompiler and compiler directives to ...
    (comp.lang.cobol)
Loading