About android4.0 emulator-arm.exe-application error, memory cannot be "read" problem solution

From: http://blog.csdn.net/blue_fire2008/article/details/6902825

 

Software environment:

Jdk1.6

Eclipse IDE for Java developers version: indigo Service Release 1 the corresponding package is: eclipse-java-indigo-SR1-win32.zip

Android SDK corresponding compressed package: android-sdk_r14-windows.zip

AndroidThe development plug-in package is adt-14.0.0.zip.

The following error occurs when creating an AVD, creating an android project, and running an application:

Emulator-arm.exe-application error: "0x0000ffff" memory referenced by the "0x0000ffff" command. The memory cannot be "read ".

The original problem occurred from360 security guardCause: Right-click the 360 security guard icon in the status bar and select the "exit" menu. The 360 security guard is completely disabled and exited.

Shut down and shut down the eclipse, and shut down the adb.exe process, restart eclipse, and the simulator application runs normally. I have repeatedly confirmed that it was caused by 360 security guards.

In addition, security guard 360 may cause the following two errors:

Emulator-arm.exe-application error: "0x00000000" memory referenced by the "0x7c931980" command. The memory cannot be "read ".

Emulator-arm.exe-application error: "0x00000000" memory referenced by the "0x7c9000069" command. The memory cannot be "read ".

360security guard does not display emulator-arm.exe-an application error. It also causes the application to directly shut down the virtual machine after the program runs.

Note:

Some netizens say that there is a space problem in the SDK path. just remove the space. But how can I directly decompress android-sdk_r14-windows.zip to drive D and rename "Android-SDK-Windows" to "android? If a space exists in the SDK path, the following problems occur:
Invalid command-line parameter: files \ Android-SDK \ tools/emulator-arm.exe.
Hint: Use '@ foo' to launch a virtual device named 'foo '.
Please use-help for more information
Instead of memory, it cannot be a "read" problem.

If the application and configuration are not modified, an error occurs when the 360 security guard is started. Otherwise, the simulator application runs normally. 360 is it difficult for security guards to blame?