Cheat Engine

[Doraneko]

Dear Dark Byte.
In reverse engineering an Android application, ceserver is very powerful and useful.
In order to make this ceserver even more useful, I would like to build it by remodeling myself.
By making some minor modifications to the source code, I succeeded in building with AndroidStudio.
However, when attaching to an application with a ceserver actually built, when the hardware breakpoint is set up, the target application will crash.

environment:
CheatEngine 6.8.1
ceserver ver: x86
Machine: NoxAppPlayer 6.2.5 androidos 7.1.2

If it is distributed as below, it works normally in the same environment.
ceserver_android_x86.zip

Android.mk I described
################################################### ######
LOCAL_PATH: = $ (call my-dir)

include $ (CLEAR_VARS)
LOCAL_CFLAGS + = - fPIE
LOCAL_LDFLAGS + = - fPIE - pie

LOCAL_MODULE: = ceserver
LOCAL_SRC_FILES: = api.c ceserver.c porthelp.c symbols.c threads.c context.c ceservertest.c extensionfunctions.c extensionloader.c
LOCAL_LDLIBS: = - lz

include $ (BUILD_EXECUTABLE)
################################################### ######

Is there something wrong with my description?

[Dark Byte]

i am not sure why the build environment would cause issues only for debugging

perhaps it also uses a different compiler which treats some typecasts different

or you're running it under a debugger (debugging debuggers in linux can be tricky as the debugged application gets debug events that the debugged app is intended to handle but the top debugger might intercept those as well)

[Doraneko]

Thank you for the reply. I also use other tools in Android analysis, but I think the performance of ceserver's dynamic analysis is very good. I am creating a debugger by myself, referring to the source code you wrote. I learned a lot of reverse engineering technology from CheatEngine. Thank you very much. I look forward to working with you.