No symbols loaded for the current document ??????

C

chandu

if i want to debug a dotnet application the break point is not going to hit.

giving the message as "The break point will not currently hit,No Symbols
have been loaded for this document".

if i rebuild once then it is working properly,if run directly with F5 it is
not going to hit the break point.

this problem is not for one applciation, for every project (even new) i am
getting this problem/

from yestarday i am fighting with this problem..

please solve...

thank u
chandu
 
M

Michael Nemtsev

Hello chandu,

Are u sure that
- u build debug version or u generate pdb in the release version
- your debug info locates nex to the executable file
?

c> if i want to debug a dotnet application the break point is not going
c> to hit.
c>
c> giving the message as "The break point will not currently hit,No
c> Symbols have been loaded for this document".
c>
c> if i rebuild once then it is working properly,if run directly with F5
c> it is not going to hit the break point.
c>
c> this problem is not for one applciation, for every project (even new)
c> i am getting this problem/
c>
c> from yestarday i am fighting with this problem..
c>
c> please solve...
c>
c> thank u
c> chandu
---
WBR, Michael Nemtsev [C# MVP].
My blog: http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo
 
C

chandu

i am generating pdb in debeg version
yes pdb is located to next to exe/

for every visual studio application i am getting same problem,and if change
the code i need to rebuild every time
for sample application i am sending this info:
'sample3.exe': Loaded 'C:\WINDOWS\system32\mscoree.dll', No symbols loaded.
'sample3.exe': Loaded 'C:\WINDOWS\system32\kernel32.dll', No symbols loaded.
'sample3.exe': Loaded 'C:\WINDOWS\system32\advapi32.dll', No symbols loaded.
'sample3.exe': Loaded 'C:\WINDOWS\system32\rpcrt4.dll', No symbols loaded.
..................................

like this giving in out put window.
 
M

Michael Nemtsev

Hello chandu,

Yep, right
The reason is that the Windows has no PDF for the system dlls.
So u need to download the debugging symbols from the MS site http://www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspx

c> i am generating pdb in debeg version
c> yes pdb is located to next to exe/
c> for every visual studio application i am getting same problem,and if
c> change
c> the code i need to rebuild every time
c> for sample application i am sending this info:
c> 'sample3.exe': Loaded 'C:\WINDOWS\system32\mscoree.dll', No symbols
c> loaded.
c> 'sample3.exe': Loaded 'C:\WINDOWS\system32\kernel32.dll', No symbols
c> loaded.
c> 'sample3.exe': Loaded 'C:\WINDOWS\system32\advapi32.dll', No symbols
c> loaded.
c> 'sample3.exe': Loaded 'C:\WINDOWS\system32\rpcrt4.dll', No symbols
c> loaded.
c> .................................
c> like this giving in out put window.
c>
c> c>
Hello chandu,

Are u sure that
- u build debug version or u generate pdb in the release version
- your debug info locates nex to the executable file
?
c> if i want to debug a dotnet application the break point is not
going
c> to hit.
c> c> giving the message as "The break point will not currently
hit,No
c> Symbols have been loaded for this document".
c> c> if i rebuild once then it is working properly,if run directly
with
F5
c> it is not going to hit the break point.
c> c> this problem is not for one applciation, for every project
(even
new)
c> i am getting this problem/
c> c> from yestarday i am fighting with this problem..
c> c> please solve...
c> c> thank u
c> chandu
---
WBR, Michael Nemtsev [C# MVP]. My blog:
http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/
"The greatest danger for most of us is not that our aim is too high
and we miss it, but that it is too low and we reach it" (c)
Michelangelo
Click to expand...
Click to expand...
---
WBR, Michael Nemtsev [C# MVP].
My blog: http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo
 
C

chandu

in that i had so many options to down load
i am using windowsxp with service pack 2

Upto that day it is debugging correctly.suddently how it happens?
i have to install windows symbols are it has any dotnet symbols packages ?

clarify on this completely please...............


Michael Nemtsev said:
Hello chandu,

Yep, right
The reason is that the Windows has no PDF for the system dlls.
So u need to download the debugging symbols from the MS site
http://www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspx

c> i am generating pdb in debeg version
c> yes pdb is located to next to exe/
c> for every visual studio application i am getting same problem,and if
c> change
c> the code i need to rebuild every time
c> for sample application i am sending this info:
c> 'sample3.exe': Loaded 'C:\WINDOWS\system32\mscoree.dll', No symbols
c> loaded.
c> 'sample3.exe': Loaded 'C:\WINDOWS\system32\kernel32.dll', No symbols
c> loaded.
c> 'sample3.exe': Loaded 'C:\WINDOWS\system32\advapi32.dll', No symbols
c> loaded.
c> 'sample3.exe': Loaded 'C:\WINDOWS\system32\rpcrt4.dll', No symbols
c> loaded.
c> .................................
c> like this giving in out put window.
c> c>
Hello chandu,

Are u sure that
- u build debug version or u generate pdb in the release version
- your debug info locates nex to the executable file
?
c> if i want to debug a dotnet application the break point is not
going
c> to hit.
c> c> giving the message as "The break point will not currently
hit,No
c> Symbols have been loaded for this document".
c> c> if i rebuild once then it is working properly,if run directly
with
F5
c> it is not going to hit the break point.
c> c> this problem is not for one applciation, for every project
(even
new)
c> i am getting this problem/
c> c> from yestarday i am fighting with this problem..
c> c> please solve...
c> c> thank u
c> chandu
---
WBR, Michael Nemtsev [C# MVP]. My blog:
http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/
"The greatest danger for most of us is not that our aim is too high
and we miss it, but that it is too low and we reach it" (c)
Michelangelo
Click to expand...
Click to expand...
---
WBR, Michael Nemtsev [C# MVP]. My blog: http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Problem with debugging after code changes 2
"No symbols loaded" 3
No symbols loaded when remote debugging 3
No Symbols loaded error - C# 3
No Symbols Loaded error in C# 3
"no symbols have been loaded for this document" 1
No symbols Loaded 4
No Symbols Have Been Loaded 2

Top