debugging, source files not shown

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Egbert Nierop (MVP for IIS) - 24 Jan 2006 12:11 GMT

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!

Reply to this Message

Oleg Starodumov - 24 Jan 2006 12:59 GMT

> 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/]

Reply to this Message

Egbert Nierop (MVP for IIS) - 24 Jan 2006 16:29 GMT

>> I have a testing win2003 machine, where I debug inside a MMC process
>> using a
[quoted text clipped - 9 lines]
>
> (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.

Reply to this Message

Oleg Starodumov - 25 Jan 2006 08:19 GMT

> 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

Reply to this Message

Egbert Nierop (MVP for IIS) - 27 Jan 2006 22:48 GMT

>> Sure it says that my DLL is loaded + 'symbols loaded'
>
[quoted text clipped - 8 lines]
> - 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 |
[quoted text clipped - 3 lines]
> for a source file not showing
> up in the debugger)

All checked.
unfortunately, no effect.

Thank you very much for your comments.

Reply to this Message

Egbert Nierop (MVP for IIS) - 22 Mar 2006 14:48 GMT

>> Sure it says that my DLL is loaded + 'symbols loaded'
>
[quoted text clipped - 24 lines]
> 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.

Reply to this Message

debugging, source files not shown

Free Magazines