John, Every compiled assembly has an associated PDB file that resides in the application binary folder. This is a binary file that describes all classes and methods in the assembly, parameter and local variable names - and any other symbols for that matter. It also contains references to source file names and line numbers in the original source.
Debuggers automatically look for this PDB file and if it is found (and there is no version mismatch between it and the compiled assembly), show you any function names (for C++ code) and classes (for C++ and other .NET languages), method and variable names They also try to find the source code on your HDD, knowing what the file locations and names are. If the source is not found, you will get a disassembly with proper symbols. If the source is there, you will get a source code view. There are other formats beside the PDB but, frankly speaking, I haven't used a debugger that utilizes a different format for a long time and I don't know what the current situation is -- maybe someone else can shed some light. Kamen Lilov -----Original Message----- From: Moderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of John Puopolo Sent: 20 Март 2003 г. 23:26 To: [EMAIL PROTECTED] Subject: [ADVANCED-DOTNET] Associating Debugged Source with Original All, As a follow-up to my last post, I have another debugger-related question. How do debuggers in .NET (or any debugger) associate original source code with executable code being debugged? Thank you, John =================================== This list is hosted by DevelopMentorR http://www.develop.com You may be interested in Guerrilla .NET, 24 March 2003, in London and Boston http://www.develop.com/courses/gdotnet View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor╝ http://www.develop.com You may be interested in Guerrilla .NET, 24 March 2003, in London and Boston http://www.develop.com/courses/gdotnet View archives and manage your subscription(s) at http://discuss.develop.com
