debugging, source files not shown

[Egbert Nierop \(MVP for IIS\)]

hi,

I have a testing win2003 machine, where I debug inside a MMC process using a
DebugBreak() statement.

But only the first time, source code was shown, after that, I only get to
see disassembly while I -did- install a debug DLL + PDB and the .CPP's in
the same directory.

I have installed visual studio 2005 without installing any language, so no
C#, or C++, only the IDE.
Native JIT debugging is enabled.

What could be done to fix this?

Thanks!

 

[Oleg Starodumov]

I have a testing win2003 machine, where I debug inside a MMC process using a
DebugBreak() statement.

But only the first time, source code was shown, after that, I only get to
see disassembly while I -did- install a debug DLL + PDB and the .CPP's in
the same directory.

Have symbols been loaded for the DLL?
Has the DLL been loaded from the correct location?

(you can check both these things in Modules window)

Regards,
Oleg
[VC++ MVP http://www.debuginfo.com/]

 

[Egbert Nierop \(MVP for IIS\)]

Have symbols been loaded for the DLL?
Has the DLL been loaded from the correct location?

(you can check both these things in Modules window)

Привет!

Sure it says that my DLL is loaded + 'symbols loaded'

The PDB also has been loaded since it is locked after debugging started.

 

[Oleg Starodumov]

Sure it says that my DLL is loaded + 'symbols loaded'

Just to be sure - it says "Symbols loaded" without any other messages
in parentheses?

The PDB also has been loaded since it is locked after debugging started.

In Call Stack window, navigate to a function which should definitely
have sources, and try something of the following:

- In Disassembly window, R-Click + Go to Source Code - will it open
the source file?

- Open the necessary source file manually and see if the debugger picks it up
(R-Click + Go to Source Code might also be tried after this)

- In Tools | Options | Debugging | General, uncheck "Require source files to exactly match
the original version"

- Check two sets of source paths available under Solution properties | Common Properties |
Debug Source Files (one allows to specify additional source directories, other can exclude
some files from source search - sometimes the latter can be responsible for a source file not showing
up in the debugger)

Oleg

 

[Egbert Nierop \(MVP for IIS\)]

Just to be sure - it says "Symbols loaded" without any other messages
in parentheses?


In Call Stack window, navigate to a function which should definitely
have sources, and try something of the following:

- In Disassembly window, R-Click + Go to Source Code - will it open
the source file?

no it has disabled the menuchoice.

- Open the necessary source file manually and see if the debugger picks it
up
(R-Click + Go to Source Code might also be tried after this)


- In Tools | Options | Debugging | General, uncheck "Require source files
to exactly match
the original version"


- Check two sets of source paths available under Solution properties |
Common Properties |
Debug Source Files (one allows to specify additional source directories,
other can exclude
some files from source search - sometimes the latter can be responsible
for a source file not showing
up in the debugger)

All checked.
unfortunately, no effect.


Thank you very much for your comments.

 

[Egbert Nierop \(MVP for IIS\)]

Just to be sure - it says "Symbols loaded" without any other messages
in parentheses?


In Call Stack window, navigate to a function which should definitely
have sources, and try something of the following:

- In Disassembly window, R-Click + Go to Source Code - will it open
the source file?

- Open the necessary source file manually and see if the debugger picks it
up
(R-Click + Go to Source Code might also be tried after this)

- In Tools | Options | Debugging | General, uncheck "Require source files
to exactly match
the original version"

- Check two sets of source paths available under Solution properties |
Common Properties |
Debug Source Files (one allows to specify additional source directories,
other can exclude
some files from source search - sometimes the latter can be responsible
for a source file not showing
up in the debugger)

For the ones interested in a solution. I found that compiling with /ZI
instead of /ZI Edit And Continue support solved the issue.