No symbols are loaded for any call stack frame. The source code cannot be displayed.

No symbols are loaded for any call stack frame. The source code cannot be displayed.

• UBFlamed

  Dear All,

  Please count us in as number 10 and 11

  We are two more developers, we have been getting the same error for some days now (No symbols are loaded for any call stack frame. The source code cannot be displayed)

  We are using C# in VS2005(release), .NET CF and the app is being run on the Device.

  For the moment this a showstopper, any Microsoft response will be highly appreciated.

  Swan B

  
  

• mrfantasy999

   

  Hi,

  I have just the same problem. So we are three already.

  Is there somone who is able to help

  regards tom

  
  
  

• NathanLiu

  Sorry we are now 5.
  
  

• Antonio Chagoury

  I had the same error message. I got mine when working with COM objects hosted in my app.

  What I did to solve this problem (if you can call it solve ) is disable the LoaderLock exception from Debug->Exceptions->Managed Debugging Assistants->LoaderLock (Remove V from Thrown).

  I don't know what's the cause of this exception but I don't get the exception anymore.

  Hope this helped at least some of you.

  Itai

  
  

• saravanan_first

  Several steps to get a more detailed debugging experience:

  1. Enable unmanaged debugging (or force mixed mode)

  2. Set the debugger to stop on all exceptions (0xc0000005 is "access violation").

  3. Turn off "just my code".

  4. Enable symbol server support and use http://msdl.microsoft.com/download/symbols for your symbol server.

  Next time you hit the exception, you should get a more complete call-stack.

  
  
  

• Erik Arfeuille

  Can we say 4 already
  
  
  

• Hooray_for_Boobies

  I'm getting the same error. Please let me know how you solved it...
  
  Thanks
  Satya
  

• Biscuit Bandit

  i am getting both errors, different places when i try to debug the code too... i am using vb.net

  thank you any help would be great!!!!

  
  
  

• Arthg2000

  I've been getting the same error for some days now. I'm using C# in VS2005 .NET CF and the app is being run on the Device Emulator. I don't get and error as such but rather a message box and Exception assistant; here are the contents of the exception that follows the message box:

  System.UriFormatException occurred
  Message="Invalid URI: The hostname could not be parsed."
  StackTrace:
  at System.Uri.CreateThis()
  at System.Uri..ctor()
  at System.Net.WebProxy.CreateProxyUri()
  at System.Net.WebProxy..ctor()
  at System.Net.HttpWebRequest.SubmitRequest()
  at System.Net.HttpWebRequest.finishGetResponse()
  at System.Net.HttpWebRequest.asyncGetResponse()
  at WorkItem.doWork()
  at System.Threading.Timer.ring()
  

  Any clues about what is going on here

  
  

• vcooking

  I just want to add that the error happens only when I run the debug version of the VSTO project. The release version does not have this problem.
  
  

• Ratzu

  This is #6.

  I am running a VSTO application.

  It is followed by the following error:

  ContextSwitchDeadlock was detected
  Message: The CLR has been unable to transition from COM context 0x158c30 to COM context 0x158950 for 60 seconds. The thread that owns the destination context/apartment is most likely either doing a non pumping wait or processing a very long running operation without pumping Windows messages. This situation generally has a negative performance impact and may even lead to the application becoming non responsive or memory usage accumulating continually over time. To avoid this problem, all single threaded apartment (STA) threads should use pumping wait primitives (such as CoWaitForMultipleHandles) and routinely pump messages during long running operations.
  

   

  
  
  

• SQLMonger66

  In the message:
       The address of the error was at 0x7a2b5aec, on thread 0x358.

  That address is very important because it can tell if you're all hitting the same crash or different crashes.  Are you all getting the same address If not, what addresses are you getting

  And this is all with the final shipped version of VS2005 (not some beta or CTP)

   

  
  
  

• Jason Maronge

  I pause to look at data while I'm at a breakpoint in my code. Often times, while attempting to step forward through my code I get an error message saying:

  "LoaderLock was detected"

  Attempting managed execution inside OS Loader lock. Do not attempt to run managed code inside a DllMain or image initialization function since doing so can cause the application to hang.

  After pressing Ok, I get the same message "No symbols are loaded for any call stack frame. The source code cannot be displayed."

  Does anyone know how to fix this Maybe this is just a coincidence, but I only noticed this in the official 2005 release and not in the beta.

  
  

• N S S

  I'm inclined to agree with this observation, in fact, I have the distinct impression in my case that the problem is related to the occurence of exception calls that are contained in System.SR.

  As these are occuring when I am using CF (which I understand doesn't naturally include it) I have tried unsuccessully to solve the problem referencing System.SR.

  This is a really annoying problem and I wish someone from MS would address it to conclusion.

  
  
• No symbols are loaded for any call stack frame. The source code cannot be displayed.