On pressing F10 or F11 debugging is ending  
Author Message
Santosh BSK





PostPosted: Visual C# IDE, On pressing F10 or F11 debugging is ending Top

Hi,

I am using VS 2005 with SP1 , C#

In my solution , i put a break point and it is getting hit. But, when i press F10 or F11 unable to continue further, just ending the debug with error :

The program '[5892] AdminLoader.exe: Managed' has exited with code -532459699 (0xe0434f4d).

I tried looking at all settings and dignostic attributes but everything is fine.


Any Ideas

kumar



Visual C#5  
 
 
TaylorMichaelL





PostPosted: Visual C# IDE, On pressing F10 or F11 debugging is ending Top

From what I understand this is the exception code used when the CLR has an unhandled exception. Are you getting a stack overflow or something This would cause the exception. What is going on when you hit the BP Are you working with unmanaged code Are you making calls into the CLR Can you create a simple test app, set a BP and step into/over it

Michael Taylor - 12/12/06

 
 
Santosh BSK





PostPosted: Visual C# IDE, On pressing F10 or F11 debugging is ending Top

 

I am not getting any stack overflow neither any exception. Application is working fine, i just want to debug to put extra code for enhancement. I even created test app in my manchine , debug is working perfect in that project. No unmanaged code is written in the class which i am trying to debug.

My application is multithreaded. I have around 10 projects in solution. I am able to debug other projects only one project among all i am unable to debug. BP is getting hit in this project but unable to proceed further, when i press F10 or F11 , its closing the running application and VS IDE coming out from debug mode. When i see output window error specified in the first msg is occuring (exited with code...). I even changed the places of BP , its hitting.

kumar


 
 
TaylorMichaelL





PostPosted: Visual C# IDE, On pressing F10 or F11 debugging is ending Top

Peculiar. What type of project is it Can you move the project to a separate solution and call it outside the normal application to eliminate problems with code interaction or threading The reason I ask is because sometimes the crash is due to outside forces. For example if you were debugging a service the SCM might time out a request if you sit at a BP for too long. A web request could also time out. In general though this won't cause a CLR crash. When the crash occurs do you get any sort of stack information Maybe through WinDbg or Dr. Watson

Michael Taylor - 12/12/06