LNK1201 error after debugging with Visual Studio .NET 2003

[Matthias Tessmann]

Hi all!

I hope this is the right group to ask, as I couldn't find
a group concerned with Visual Studio .NET only.

So here is the problem I constantly experience and I was
wondering if this is a Visual Studio bug and whether a workaround
to this exists (note, I don't use any of the managed stuff, i.e. I don't
use .NET but plain old C++ and Assembly):

Whenever I debug my code in VS and switch to assembly view (STRG-ALT-D),
step throug the assembler code line by line (doesn't matter if its my own or
the cl generated
assembly code), then hit "Stop Debugging", change something in the code and
debug again,
VS fails to recompile by telling me

LINK : fatal error LNK1201: error writing to program database
'InsertProjectNameAndDirectoryHere.pdb';
check for insufficient disk space, invalid path, or insufficient privilege

The only way that I can go on is by closing VS and re-opening, which
to put it this way, can be very annoying :-(

Also this only happens when debugging assembler code...if I step through C++
code
only everything works perfectly well.

I would be glad if anybody knows this problem and also knows if I can do
something
about it.

Thank you in advance for your replies.

Matthias

 

[Gary Chang]

Hi Matthias,

Whenever I debug my code in VS and switch to assembly view (STRG-ALT-D),
step throug the assembler code line by line (doesn't matter if its my own or
the cl generated
assembly code), then hit "Stop Debugging", change something in the code and
debug again,
VS fails to recompile by telling me ...

We have some known LNK1201 issues logged in internal database, such as
large .pdb file size, anti-virus program concerns and so on. However I
don't find such a case like you described that only happens when debugging
assembler code, and I am not able to repro this behavior on my side, so
does this annoying behavior occur only on your current working machine or
also on other machines?

My suggestion is to delete the .pdb file or do a VS.NET Reparation, maybe
that will fix your problem.

And if the above methods still don't work for your problem, how about
disable the option of Project/Properties.../C/C++/General/Debug Information
Format?


Thanks!

Best regards,

Gary Chang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------

 

[Matthias Tessmann]

Hello Gary,

does this annoying behavior occur only on your current working machine or
also on other machines?

I'm afraid but I only have one machine, so I was not able to test
it on another one.

And if the above methods still don't work for your problem, how about
disable the option of Project/Properties.../C/C++/General/Debug Information
Format?

Due to this I experimented with the debug database switches, and as it
seems,
the default "Debug Database for Edit & Continue" is the only one that
produces
the miss-behaviour. Now I changed that to "Debug Database" only, and it
seems
to work now as expected, at least I ran some debugging tests and didn't
experience
the problem again - I hope it stays like that.

Thank you for your help and pointing me into the right direction

Matthias

 

[Gary Chang]

Hi Matthias

Thanks for your quickly response!

I am delight to know you have resolved the problem and it is my pleasure
assisting you on this issue.


Best regards,

Gary Chang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------