Debugging and linking conflicts with VC50.PDB 
Author Message
 Debugging and linking conflicts with VC50.PDB

We have several programmers working on individual components for a
project with a container.  When one of us is debugging his component
using the container, the other can't link the container because the
VC50.PDB file is locked.  We were able to get around this problem for
the container's .PDB file by releasing it along with the .EXE into a
path that all of us have in our executable path.  Unfortunately, there
is a VC50.PDB for all C++ projects.  How can we get around this as well?
A speedy tip may prevent {*filter*} from breaking out among the masses

Sun, 02 Jul 2000 03:00:00 GMT  
 [ 1 post ] 

 Relevant Pages 

1. Debugging and linking conflicts with VC50.PDB

2. When is VC50.PDB needed?

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

4. Unable to open vc50.pdb

5. How Can I Eliminate VC50.PDB?

6. error writing to vc50.pdb ???

7. When is VC50.PDB needed?

8. error writing to vc50.pdb ???

9. error writing to vc50.pdb ???

10. C2859 error (precomp header vs .pdb conflict)

11. Debug in VC50

12. debugging using pdb files


Powered by phpBB® Forum Software