JIT Debugging problem in VC++ 2005

JIT Debugging problem in VC++ 2005

• ABOH

  That just tells you to make sure that all previous versions of visual studio 2005 are uninstalled. Beta 1, Beta 2 and the release candidate were publically available so users could have them installed. This is telling the user that upgrades or overwrites from previous versions are not supported.
  Anyway, can you attach the ide to a process yourself to debug.

  
  
  

• msorrent

  I am not working with Express editions or Beta versions. There are two versions of Visual Studio: 98 and 2005. This must be supported, and it works properly on other computers.
  I can think about some workaround like defining VC++ 6.0 as default debugger, but is there solution for 2005 debugger
  

• James Terwilliger

  One possible reason for this is the the current process doesn't have the necessary permission to start the debugger.
  
  

• Mochiwala

  I still use "Attach to process" function.
  

• woolybutt

  The same happens with managed applications. The problem is in JIT debugger. I am working with account from Administrator group.
  

• Simon_-_Yang

  Alex, did you ever figure out the problem

  I am having a similar problem with my JIT installation, see

  http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=594772&SiteID=1

  Thanks!

  
  
  

• JMarkHowell

  Addintinal information. I run application which contains Null-pointer assignment. When Exception dialog is opened, I select "Debug", but debugger doesn't start. Two messages are added to Application Event Log:
  
  1. An unhandled win32 exception occurred in Test.exe [3208]. Just-In-Time debugging this exception failed with the following error: The remote procedure call failed.

  Check the documentation index for 'Just-in-time debugging, errors' for more information.
  
  Data:
  0000: be 06 07 80
  
  2. Faulting application test.exe, version 0.0.0.0, faulting module test.exe, version 0.0.0.0, fault address 0x00011388.

  
  

• EWoodruff

  Additional information: if I change AeDebug Debugger entry in the Registry to
  "C:\Program Files\Microsoft Visual Studio\Common\MSDev98\Bin\msdev.exe" -p %ld -e %ld
  VC++ 6.0 debugger successfully starts. But vsjitdebugger.exe doesn't work.
  

• aydinserkan

  Doesn't it say on the Visual C++ web site thing for VC++ 2005 you need to unistall all previous versions of it. You have VS 98 and VS 2005 and I believe the website is telling you to remove VS 98.
  
  http://msdn.microsoft.com/vstudio/express/visualc/download/
  
  

• yonderstar

  Well, VC++ 6.0 option is not so good, because VC++ 6.0 doesn't show source code. So, attaching to process is the only workaround.
  

• thenujay

  I didn't disable any service after Windows installation. RPC service is active. Is there any specific service I can check
  For future reference, I have two workarounds. For somebody who works only with unmanaged code, it is possible to set VC++ 6.0 as active debugger, as described in one of my previous posts.
  To activate VS 2005 JIT debugger when program reports exception, it is possible to attach to this process from VS 2005, and after this press Debug in the exception dialog. Not perfect, but I can live with this.
  

• JonasSam

  From the event log, this looks like RPC is not working correctly on your computer:
  
  An unhandled win32 exception occurred in Test.exe [3208]. Just-In-Time debugging this exception failed with the following error: The remote procedure call failed.
  
  That error is the system error RPC_S_CALL_FAILED. Do you have any RPC related services disabled on your computer

  
  
  
• JIT Debugging problem in VC++ 2005