Re: Compiler randomly cant access vc70.pdb or vc70.idb
- From: "Tom Serface" <tserface@xxxxxxx>
- Date: Tue, 7 Mar 2006 08:44:27 -0800
Are you building more than one thing at a time (different windows perhaps)
and are any of them using the same .pdb file (the default name is vc70.pdb).
You can rename the .pdb files so that each program has its own and maybe
that will help. Just a thought.
Tom
<jjbott@xxxxxxxxx> wrote in message
news:1141744789.986858.85690@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello! We're having a strange problem with compiling our solutions with
VS.NET 2003. On our build server, the build (from command line) will
usually fail at some point because the compiler can't acces vc70.pdb or
vc70.idb. Does anyone know why that might be, and what we can do to fix
it? It seems like the compiler is blocking itself from the files. I've
noticed that the problem always seems to occur after a "Compiling..."
line in the build logs. It fails for a few files, then keeps on
trucking until the next "Compiling..." line.
...
something1.cpp
something2.cpp
Compiling...
something3.cpp
something3.cpp(0) : fatal error C1033: cannot open program database
'somewhere\release\vc70.pdb'
something4.cpp
something4.cpp.cpp(0) : fatal error C1033: cannot open program database
'somewhere\release\vc70.pdb'
something5.cpp
something6.cpp
something7.cpp
something8.cpp
something9.cpp
something10.cpp
something11.cpp
something12.cpp
Compiling...
something13.cpp
something13.cpp(0) : fatal error C1033: cannot open program database
'somewhere\release\vc70.pdb'
something14.cpp
something14.cpp(0) : fatal error C1033: cannot open program database
'somewhere\release\vc70.pdb'
something15.cpp
something15.cpp(0) : fatal error C1033: cannot open program database
'somewhere\release\vc70.pdb'
something16.cpp
something16.cpp(0) : fatal error C1033: cannot open program database
'somewhere\release\vc70.pdb'
something17.cpp
something17.cpp(0) : fatal error C1033: cannot open program database
'somewhere\release\vc70.pdb'
something18.cpp
something19.cpp
something20.cpp
something21.cpp
something22.cpp
...
It doesnt fail very often, but since our program is so huge it almost
always fails somewhere. It always fails in a different spot too. If we
start the build over without cleaning the solutions first, it will
eventually finish the build with no errors. So far this hasnt happened
on my development machine, which makes it extra frustrating. We've
recently migrated from VC6 to VC7.1. With VC6 we'd hit this problem
very rarely, so it was only an occasional annoyance. Now, since our SOP
is to start clean with every production build, it's hard to get a build
that finishes with no errors.
Thanks for any insight,
Joe
.
- Follow-Ups:
- References:
- Compiler randomly cant access vc70.pdb or vc70.idb
- From: jjbott
- Compiler randomly cant access vc70.pdb or vc70.idb
- Prev by Date: Compiler randomly cant access vc70.pdb or vc70.idb
- Next by Date: Re: Compiler randomly cant access vc70.pdb or vc70.idb
- Previous by thread: Compiler randomly cant access vc70.pdb or vc70.idb
- Next by thread: Re: Compiler randomly cant access vc70.pdb or vc70.idb
- Index(es):
Relevant Pages
|
