CODEWITHSUNDEEP
c#visual-studio-debugging
Rishikesh
Rishikesh

Reputation: 496

Regarding PDB usage

Its always recommended to store the PDB files for each public build so that we can debug if there is any issue on Production server.

My doubt is if my source code is changed even due to addition of two lines whether i will be able to debug when i run the program and try to attach it to my debugger? In my understanding since PDB contains the line no. and local variable only,if the source code is changed we can't debug , so how its helpful unless we go back to original source which created the dll but if we know the source file then why we need the original pdb since we can replace it our local pdb. I am sure i am missing something here..Will be glad if you clear this.

Upvotes: 0

Views: 119

Answers (1)

bloudraak
bloudraak

Reputation: 6002

When using a symbol server with a source server, you should be able to debug binaries (or a dump from a customer) without requiring access to the source that produced the modules and symbols. It is tremendously helpful.

We update both servers for every build, which allows us to debug an application in a QA environment even if we do not have the source code on disk.

PDB files on their own isn't too helpful if the source that produced them is missing.

Upvotes: 2

Related Questions