GetLastError() - 0x00000032

:출처: http://www.compulogy.org/?tag=0x00000032

ERROR_NOT_SUPPORTED

Tags: 0x00000032, 32, 32-bit, 50, 64, 64-bit, debugging, error_not_supported, grayhat, grayhat coding, python, seitz, windows

While running code examples from the awesome “Gray Hat Python” book by Justin Seitz, I kept getting the ERROR_NOT_SUPPORTED (error code 0×00000032) error while trying to attach to a running process using the DebugActiveProcess call in the Microsoft Windows kernel32.dll shared library. Other folks seem to have had the same problem. Fortunately, after some brief reading of the Microsoft’s MSDN pages, the problem turns out to be rather trivial.

According to MSDN page on Win32 error codes, the ERROR_NOT_SUPPORTED code indicates that (what a surprise!) the request is not supported. That is, the call to the DebugActiveProcess method is not supported for the particular application (a python-based debugger in this case).  The MSDN page on kernel and user mode states that “a processor in a computer running Windows has two different modes: user mode and kernel mode. [...]  Applications run in user mode, and core operating system components run in kernel mode.” Finally, on the MSDN page on choosing the 32-Bit or 64-Bit debugging tools, we find that debugging live user-mode code that is running on the same computer as the debugger requires the use of the 64-bit tools for debugging 64-bit code (and 32-bit code running on WOW64).

So the solution to the above problem is simply to install the 64-bit version of the Python interpreter. And don’t forget to set the 64-bit interpreter in the project settings in case you’re using Eclipse following the recommendation in Seitz’s book.

 

##########################################################

결론 :::::  32bit python을 64bit 환경에서 사용하면 안된다~!!!