468,249 Members | 1,510 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 468,249 developers. It's quick & easy.

"no symbols loaded"

When I debug my application I get "no symbols loaded"

=================
'DefaultDomain': Loaded 'c:\winnt\microsoft.net\framework\v1.1.4322\mscorl ib.dll', No symbols loaded.
'MHSFire': Loaded 'C:\Documents and Settings\bamason\My Documents\Visual Studio Projects\MHSFire\bin\MHSFire.exe', Symbols loaded.
'MHSFire.exe': Loaded 'c:\winnt\assembly\gac\system.windows.forms\1.0.50 00.0__b77a5c561934e089\system.windows.forms.dll', No symbols loaded.
'MHSFire.exe': Loaded 'c:\winnt\assembly\gac\system\1.0.5000.0__b77a5c56 1934e089\system.dll', No symbols loaded.
'MHSFire.exe': Loaded 'c:\winnt\assembly\gac\system.drawing\1.0.5000.0__ b03f5f7f11d50a3a\system.drawing.dll', No symbols loaded.
'MHSFire.exe': Loaded 'c:\winnt\assembly\gac\system.data\1.0.5000.0__b77 a5c561934e089\system.data.dll', No symbols loaded.
'MHSFire.exe': Loaded 'c:\winnt\assembly\gac\system.xml\1.0.5000.0__b77a 5c561934e089\system.xml.dll', No symbols loaded.
'MHSFire.exe': Loaded 'c:\winnt\assembly\gac\microsoft.visualbasic\7.0.5 000.0__b03f5f7f11d50a3a\microsoft.visualbasic.dll' , No symbols loaded.
'MHSFire.exe': Loaded 'c:\winnt\assembly\gac\accessibility\1.0.5000.0__b 03f5f7f11d50a3a\accessibility.dll', No symbols loaded.
The program '[2152] MHSFire.exe' has exited with code 0 (0x0).
======================
I 've used the ngen command to create native images, but it still generates these errors.

I am not able to compile in release mode without the same errors.

Anyone have any ideas?

Nov 22 '05 #1
1 2326
Ok, part of the problem was fixed by going to KB Article 319037 and specifying the path to the Microsoft symbol server.

This fixed the problem in debug mode, but did when I went to build in release mode. Also, it was not able to locate server symbols for the accessibility.dll or microsoft.visualbasic.dll.

Does anyone know how to find symbols for these libraries?

"aerobar2" wrote:
When I debug my application I get "no symbols loaded"

=================
'DefaultDomain': Loaded 'c:\winnt\microsoft.net\framework\v1.1.4322\mscorl ib.dll', No symbols loaded.
'MHSFire': Loaded 'C:\Documents and Settings\bamason\My Documents\Visual Studio Projects\MHSFire\bin\MHSFire.exe', Symbols loaded.
'MHSFire.exe': Loaded 'c:\winnt\assembly\gac\system.windows.forms\1.0.50 00.0__b77a5c561934e089\system.windows.forms.dll', No symbols loaded.
'MHSFire.exe': Loaded 'c:\winnt\assembly\gac\system\1.0.5000.0__b77a5c56 1934e089\system.dll', No symbols loaded.
'MHSFire.exe': Loaded 'c:\winnt\assembly\gac\system.drawing\1.0.5000.0__ b03f5f7f11d50a3a\system.drawing.dll', No symbols loaded.
'MHSFire.exe': Loaded 'c:\winnt\assembly\gac\system.data\1.0.5000.0__b77 a5c561934e089\system.data.dll', No symbols loaded.
'MHSFire.exe': Loaded 'c:\winnt\assembly\gac\system.xml\1.0.5000.0__b77a 5c561934e089\system.xml.dll', No symbols loaded.
'MHSFire.exe': Loaded 'c:\winnt\assembly\gac\microsoft.visualbasic\7.0.5 000.0__b03f5f7f11d50a3a\microsoft.visualbasic.dll' , No symbols loaded.
'MHSFire.exe': Loaded 'c:\winnt\assembly\gac\accessibility\1.0.5000.0__b 03f5f7f11d50a3a\accessibility.dll', No symbols loaded.
The program '[2152] MHSFire.exe' has exited with code 0 (0x0).
======================
I 've used the ngen command to create native images, but it still generates these errors.

I am not able to compile in release mode without the same errors.

Anyone have any ideas?

Nov 22 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by aerobar2 | last post: by
3 posts views Thread by Lou | last post: by
1 post views Thread by Edward King | last post: by
10 posts views Thread by RDI | last post: by
8 posts views Thread by Steve Kershaw | last post: by
1 post views Thread by Scott McFadden | last post: by
reply views Thread by NPC403 | last post: by
reply views Thread by zattat | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.