c# - Killing a process -
We have been developing that for Windows Server 2003, but since Windows Server 2008 R2 issues this migration There is a custom application.
Part of the application / process is to kill a Windows process with the C # code. It works fine on Windows 2003, but Windows 2008 R2 fails to kill the code process. Anyone has come across anything like this or has any idea what the problem might be?
Text after "div class =" itemprop = "text">
Exception code: 0xe053534f
The name is always inspirational when there is a problem with Microsoft programmers often raising an exception code that can decode the abbreviation of 3 characters. The exception code for the C + + exception is 0xe04d5343, the last 3 hex bytes decode "MSC", "Microsoft C ++", the exception code for a managed exception is 0xe0434f4d, "COM +" which was the initial name of .net.
Give your exception the same treatment and you will get "SSO" which means "soft stack overflow" is like a regular stack overflow, except that the system knows it can predict it That, if this completes the call, then Program will bomb because you do not save enough stack space.
What exactly does your app stack bomb over the overflow, is not clear from the information you provided. You have to debug it.
Comments
Post a Comment