CSharp/C#, Debugging with just PDB files

1. Unable to debug DLL with PDB files - CSharp/C#

2. debugging with a pdb file

hello, all,

my problem: my company sells an COM component compiled in VS6 using ATL. one of
our valued customers is having some problems with a beta version of our
component; it crashes their app. they develop in VSdotNET.

i am considering the possibility of providing them with a pdb file along with
the other stuff we would normally give them to test. i understand that this
requires some trust on our part. that is not an issue in this case.

i am exploring the various makefile params needed to generate the single pdb 
file and may have questions on that aspect later; but first i want to understand 
better what can be accomplished with the pdb file and how i might observe that 
functionality on my dev machine.

suppose i have succeeded in creating MyCOMstuff.pdb.
what must i do in a VS6 client to experience the utility of the pdb file?
assume the MyCOMstuff.dll component is registered on my system and its pdb file 
is sitting in the same folder as my client exe.

now what do i do?
will i be able to step into method calls to my component?

thanks for any help on this matter.
i can't seem to find a lucid discussion of it anywhere.

3. debugging using pdb file

4. Debugging: obtaining symbol and line from address using .pdb file

I have code to obtain information on crashes which has been tried and 
works - on Windows Server 2003, at least. However, for some reason I cannot 
obtain symbol and line information when an executable (not the same as the 
one tried on Windows Server 2003: that was the simplest case just to 
establish that the code works) crashes on Windows 2000 Server, Service Pack 
4. The latest Debugging Tools for Windows (6.6.7.5) have been installed and 
dbghelp.dll placed in the same directory as the executable. The code is 
compiled using Visual Studio 2005.

The StackWalk64 seems to be OK, too, and it only when it comes to the symbol 
and the line that the code fails.

If a particular address points to, say, KERNEL32.dll, I do get the symbol 
(not the file or the line, though, but this is obviously fine) but never for 
my own executable.

The .pdb file for the executable is placed together with it in the same 
directory (it should be noted that the code is compiled on a different 
machine, so the path to the .pdb file saved in the executable will be 
incorrect). I do not modify the path and SymGetSearchPath() returns 
".;F:\WINNT\Symbols" (the current directory is in, that is).

For both SymGetSymFromAddr64() (SymFromAddr()) and SymGetLineFromAddr64(), 
GetLastError() returns "Attempt to access invalid address."

Thank you.

Paul 

5. locking of the .pdb file upon program crash in debug mode

6. PDB debug file size limit in Visual C++ 6.0 - article ID 238875

Hello all,
I would like to know if anybody knows of a solution for the 64 MB size limit 
on the PDB file in Visual C++ 6.0
The ones described in the article are not helpful.
Solution could be:
- a patch to Visual 6.0?
- a build option that would increase this limit?
- a build option that would use other type of debug info without this kind 
of limit?

Any info would be helpful here!

Thanks a lot in advance.
Cristian

7. Debugging, PDB files

8. Unexpected error creating debug information file .pdb

i dont know , what's the reson of this, but if i complile my solution in 
release mode , it works , but  give buid error in Debug mode -- "Unexpected 
error creating debug information file  .pdb". Project is on .net 1.0 
framework. Error came after i installed framework 2.0 from net. but now i 
uninstalled it. but facing same problem , i have also tried repair from 
VS.net setup, pls tell me if anyone get solution of this..

-- 
Nitin Arora
E S Technology Ltd
 XXXX@XXXXX.COM 
India