DEBUGGABLE_UDEBONLY

DEBUGGABLE_UDEBONLY

Use the DEBUGGABLE_UDEBONLY statement to mark only the debug version of application to be debugged using the run-mode debug API.

If both DEBUGGABLE_UDEBONLY and debuggable are in an .mmp file, the behaviour will follow as DEBUGGABLE_UDEBONLY.

The following examples show the different scenarios when using the keywords debuggable and DEBUGGABLE_UDEBONLY:

• Perform the following steps using the keyword debuggable:

  1. Add keyword debuggable into helloworld.mmp file

  2. Build helloworld.mmp

  3. Execute READIMAGE to dump helloworld.exe (release and debug version).

     The expected result is 0x00000800, which means the executable file is debuggable.

• Perform the following steps using the keyword DEBUGGABLE_UDEBONLY:

  1. Add keyword DEBUGGABLE_UDEBONLY into helloworld.mmp file

  2. Build helloworld.mmp

  3. Execute READIMAGE to dump helloworld.exe (release and debug version).

     The expected result is that the debug version of the executable file is debuggable but, the release executable file is not debuggable.

• Perform the following steps using both DEBUGGABLE_UDEBONLY and debuggable keywords:

  1. Add both DEBUGGABLE_UDEBONLY and debuggable keywords into helloworld.mmp file.

  2. Build helloworld.mmp file

  3. Execute READIMAGE to dump helloworld.exe (release and debug version).

     The expected result is that the debug version of the executable file is debuggable but, the release executable file is not debuggable.