How Can I Eliminate VC50.PDB? 
Author Message
 How Can I Eliminate VC50.PDB?

My Question:

My question is how to get the debug version of my
projects to produce a single .pdb file with a
project specific name that contains all the debug
info.

Why I want to do this:

The debug version of my projects all produce 2
.pdb files.  vc50.pdb and <project name>.pdb.  The
problem with producing the vc50.pdb is that I have
several DLLs and they will all be installed in the
same directory by the install.  

So the DEBUG version of the product will only be
able to have ONE of the vc50.pdbs.  This causes
frequent requests from the de{*filter*} for the
vc50.pdb and claims that the one found is not the
right one.

What I Tried:

The project options contains this option
/Fd"Debug/".  I changed it to
/Fd"<project name>.pdb".  This got rid of the
vc50.pdb and made the <project name>.pdb file
larger but I found that VC++ IDE would crash with
a stack overflow when I tried to step into or even
set a breakpoint in any project with this
modification.

Dave L

--
No eMail please, post replies.  If you must eMail, remove the obvious
obfuscation



Sat, 22 Jul 2000 03:00:00 GMT  
 How Can I Eliminate VC50.PDB?

Quote:

>My Question:

>My question is how to get the debug version of my
>projects to produce a single .pdb file with a
>project specific name that contains all the debug
>info.

From with the Project Settings dialog box (ALT-F7) select the C/C++ tab and
change "Program Database:" to "C7 compatible".  This includes the C7
(CodeView/MSC7) debug information rather than exporting it to a .pdb (thus
bloating all your objs, exes, and dlls).

Tom



Mon, 24 Jul 2000 03:00:00 GMT  
 How Can I Eliminate VC50.PDB?

Quote:

>My Question:

>My question is how to get the debug version of my
>projects to produce a single .pdb file with a
>project specific name that contains all the debug
>info.

>Why I want to do this:

>The debug version of my projects all produce 2
>.pdb files.  vc50.pdb and <project name>.pdb.  The
>problem with producing the vc50.pdb is that I have
>several DLLs and they will all be installed in the
>same directory by the install.

>So the DEBUG version of the product will only be
>able to have ONE of the vc50.pdbs.  This causes
>frequent requests from the de{*filter*} for the
>vc50.pdb and claims that the one found is not the
>right one.

In VC5 MS changed the debug information to stop lumping in the type
information into the main final PDB file.  What you need to do is set the
option "no seperate types" in the debug/output selection of your link tab.
Then you end up with a myexe.exe and myexe.pdb and mydll.dll and mydll.pdb

Regards,
John



Mon, 24 Jul 2000 03:00:00 GMT  
 
 [ 3 post ] 

 Relevant Pages 

1. When is VC50.PDB needed?

2. Question: Debugger Can't find vc50.pdb

3. Unable to open vc50.pdb

4. Debugging and linking conflicts with VC50.PDB

5. error writing to vc50.pdb ???

6. Debugging and linking conflicts with VC50.PDB

7. When is VC50.PDB needed?

8. error writing to vc50.pdb ???

9. error writing to vc50.pdb ???

10. using FAULT address of EXE sans .pdb in EXE with .pdb

11. PDB API / COFF and PDB file formats

12. Determining what canned preprocessor symbols are available

 

 
Powered by phpBB® Forum Software