SharpDevelop Community

Get your problems solved!
Welcome to SharpDevelop Community Sign in | Join | Help
in Search

Can't find a Solution to this one. Can it be solved?

Last post 12-11-2009 9:07 AM by darkcloud. 6 replies.
Page 1 of 1 (7 items)
Sort Posts: Previous Next
  • 09-22-2009 4:44 AM

    Can't find a Solution to this one. Can it be solved?

    This one is really getting me down. I can't find any info on this on the web and urgently need to solve it. The debugger was working well up to resently so its either a config issue, dependancy issue or a compiler issue but I can't see where.  Can anyone give me a heads up

     

    SharpDevelop Version : 3.1.0.4545
    .NET Version         : 2.0.50727.3074
    OS Version           : Microsoft Windows NT 6.0.6001 Service Pack 1
    Current culture      : English (Australia) (en-AU)
    Current UI language  : en-US
    Terminal Server Session
    Working Set Memory   : 129544kb
    GC Heap Memory       : 54226kb

    Exception thrown:
    System.Runtime.InteropServices.COMException (0x80131323): Cannot use JMC on this code (likely wrong JIT settings). (Exception from HRESULT: 0x80131323)
       at Debugger.Interop.CorDebug.ICorDebugModule2.SetJMCStatus(Int32 bIsJustMyCode, UInt32 cTokens, UInt32& pTokens)
       at Debugger.Module.ResetJustMyCodeStatus()
       at Debugger.Module..ctor(Process process, ICorDebugModule pModule)
       at Debugger.Process.AddModule(ICorDebugModule corModule)
       at Debugger.ManagedCallback.LoadModule(ICorDebugAppDomain pAppDomain, ICorDebugModule pModule)
       at Debugger.ManagedCallbackSwitch.LoadModule(ICorDebugAppDomain pAppDomain, ICorDebugModule pModule)
       at Debugger.ManagedCallbackProxy.<>c__DisplayClass1c.<LoadModule>b__1b()
       at Debugger.Interop.MTA2STA.<>c__DisplayClass3.<EnqueueCall>b__0()
       at Debugger.Interop.MTA2STA.PerformCall()
       at Debugger.Interop.MTA2STA.PerformAllCalls()
       at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)
       at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
       at System.Threading.ExecutionContext.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
       at System.Windows.Forms.Control.InvokeMarshaledCallbacks()

    ---- Recent log messages:
    12:22:08.866 [1] DEBUG - Debugger: Process has queued callbacks
    12:22:09.007 [1] DEBUG - Debugger: Callback: LoadAssembly
    12:22:09.007 [1] DEBUG - Debugger: Process has queued callbacks
    12:22:09.038 [1] DEBUG - Debugger: Callback: LoadModule C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files oot\fb599c57\910982b\App_Web_imig6h9x.dll
    12:22:09.053 [1] DEBUG - Debugger: Process has queued callbacks
    12:22:09.053 [1] DEBUG - Debugger: Callback: LoadAssembly
    12:22:09.053 [1] DEBUG - Debugger: Process has queued callbacks
    12:22:09.053 [1] DEBUG - Debugger: Callback: LoadModule C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files oot\fb599c57\910982b\App_Web_vkamdnjm.dll
    12:22:09.069 [1] DEBUG - Debugger: Process has queued callbacks
    12:22:09.069 [1] DEBUG - Debugger: Callback: LoadAssembly
    12:22:09.069 [1] DEBUG - Debugger: Process has queued callbacks
    12:22:09.069 [1] DEBUG - Debugger: Callback: LoadModule C:\Windows\assembly\GAC_MSIL\System.Drawing\2.0.0.0__b03f5f7f11d50a3a\System.Drawing.dll
    12:22:09.069 [1] DEBUG - Debugger: Process has queued callbacks
    12:22:09.069 [1] DEBUG - Debugger: Callback: LoadAssembly
    12:22:09.069 [1] DEBUG - Debugger: Process has queued callbacks
    12:22:09.069 [1] DEBUG - Debugger: Callback: LoadModule C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files oot\fb599c57\910982b\App_Web__xy4mpxx.dll
    12:22:09.131 [1] DEBUG - Debugger: Process has queued callbacks
    12:22:09.225 [1] DEBUG - Debugger: Callback: LoadAssembly
    12:22:09.225 [1] DEBUG - Debugger: Process has queued callbacks
    12:22:09.241 [1] DEBUG - Debugger: Callback: LoadModule C:\Windows\assembly\GAC_MSIL\System.Web.Services\2.0.0.0__b03f5f7f11d50a3a\System.Web.Services.dll
    12:22:09.241 [1] DEBUG - Debugger: Process has queued callbacks
    12:22:09.241 [1] DEBUG - Debugger: Callback: LoadAssembly
    12:22:09.241 [1] DEBUG - Debugger: Process has queued callbacks
    12:22:09.241 [1] DEBUG - Debugger: Callback: LoadModule C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files oot\fb599c57\910982b\assembly\dl3\6b89222e\b02ee946_3022ca01\Gios Pdf.NET.DLL
    12:22:09.241 [1] ERROR - ThreadException caught
    --> Exception:
    System.Runtime.InteropServices.COMException (0x80131323): Cannot use JMC on this code (likely wrong JIT settings). (Exception from HRESULT: 0x80131323)
       at Debugger.Interop.CorDebug.ICorDebugModule2.SetJMCStatus(Int32 bIsJustMyCode, UInt32 cTokens, UInt32& pTokens)
       at Debugger.Module.ResetJustMyCodeStatus()
       at Debugger.Module..ctor(Process process, ICorDebugModule pModule)
       at Debugger.Process.AddModule(ICorDebugModule corModule)
       at Debugger.ManagedCallback.LoadModule(ICorDebugAppDomain pAppDomain, ICorDebugModule pModule)
       at Debugger.ManagedCallbackSwitch.LoadModule(ICorDebugAppDomain pAppDomain, ICorDebugModule pModule)
       at Debugger.ManagedCallbackProxy.<>c__DisplayClass1c.<LoadModule>b__1b()
       at Debugger.Interop.MTA2STA.<>c__DisplayClass3.<EnqueueCall>b__0()
       at Debugger.Interop.MTA2STA.PerformCall()
       at Debugger.Interop.MTA2STA.PerformAllCalls()
       at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)
       at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
       at System.Threading.ExecutionContext.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
       at System.Windows.Forms.Control.InvokeMarshaledCallbacks()

    Filed under:
  • 09-22-2009 6:21 AM In reply to

    • siegi44
    • Top 25 Contributor
    • Joined on 03-31-2006
    • Steyr, Austria
    • Posts 269
    • Team Members

    Re: Can't find a Solution to this one. Can it be solved?

    Hi,

    please check if you are trying to run a release build with the debugger attached. This is not supported.

    I cannot think of any other situation where this could happen.

    regards,

    Siegfried

  • 09-22-2009 7:41 AM In reply to

    Re: Can't find a Solution to this one. Can it be solved?

    Siegfried,

    thanks for the fast responce. I've checked the project settings and recompiled again with the same result.

    Any other possible casues of the above exception?  Could a reference dll be causing it? I've also tried turning of the JIT debugging but no success yet.

    Talk soon

    Derryck

  • 09-22-2009 1:15 PM In reply to

    • DavidSrbecky
    • Top 10 Contributor
    • Joined on 08-22-2005
    • Usti nad Labem, Czech Republic
    • Posts 461
    • Team Members

    Re: Can't find a Solution to this one. Can it be solved?

    The last log message before the exception is "12:22:09.241 [1] DEBUG - Debugger: Callback: LoadModule C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files oot\fb599c57\910982b\assembly\dl3\6b89222e\b02ee946_3022ca01\Gios Pdf.NET.DLL"

    My best guess it that the debugger found the "Pdf.NET.pdb" symbol file and therefore tried to load the dll as if were a debug-build dll (release-build would not have a pdb symbol file).  Unfortunately the dll was acutally release-build and thus it failed.  I have tried it - debug-build dll loads fine even if the main application is release-build, but release-build dll with existing pdb file throws this exception.

    To fix it, try deleteing the file "Pdf.NET.pdb".

  • 09-23-2009 12:45 AM In reply to

    Re: Can't find a Solution to this one. Can it be solved?

    Thanks very much, that makes sense. It was the last project I compiled when working on this job two weeks ago. I must have compiled a release version, don't know why though as this is still only a alpha/ test version and I was actually debugging that project. Still I was in a rush and as you probably know you some times do silly things when your stressed.

    I've removed the pdb file and all is good. Thanks a million.

    Derryck

    P.S I hope this thread helps others in a similar bind, as the other threads here with similar issues did not have a resolution

  • 11-18-2009 7:36 PM In reply to

    • DavidSrbecky
    • Top 10 Contributor
    • Joined on 08-22-2005
    • Usti nad Labem, Czech Republic
    • Posts 461
    • Team Members

    Re: Can't find a Solution to this one. Can it be solved?

    As of r5265 this should work without the workaround.

  • 12-11-2009 9:07 AM In reply to

    Re: Can't find a Solution to this one. Can it be solved?

    Thanks, that helped me too.

     

    I was thinking maybe the problem is that IIS is running as 64 bit proc, and my web server cassini is running 32 bit, and then my app is compiled as any cpu.   heck, i really got mixed. Now it works fine.

     

    Thanks!

Page 1 of 1 (7 items)
Powered by Community Server (Commercial Edition), by Telligent Systems
Don't contact us via this (fleischfalle@alphasierrapapa.com) email address.