[supercachai]

Update: after debugging with the emulator it works on the device. Thanks for that fix!

I still get that assertion error when running a toolchain test though, leaving the toolchain untested. Can I somehow disable the dialog that asks for testing an untested toolchain?

[supercachai]

Thanks,

this gets the gdb started, I get a loading bar that it waits for the application to start but then crashes again (with a note to try 32-bit version NDK, tried it but same result):

~"/s/ndk-toolchain/src/build/../gdb/gdb-7.7/gdb/gdbarch.c:3991: internal-error: gdbarch_record_special_symbol_p: Assertion `gdbarch != NULL' failed.\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable.\nQuit this debugging session? "
~"(y or n) [answered Y; input not from terminal]\n"
~"/s/ndk-toolchain/src/build/../gdb/gdb-7.7/gdb/gdbarch.c:3991: internal-error: gdbarch_record_special_symbol_p: Assertion `gdbarch != NULL' failed.\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable.\nCreate a core file of GDB? "
~"(y or n) [answered Y; input not from terminal]\n"
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.


[supercachai]

Hi, I just encountered the same issue, with a Nexus 5X. My logs are equal, VisualGDB somehow assumes “arm64”, where it should be “arm64-v8a”. I’ve set some symlinks from “arm64” to “arm64-v8a” in lib and obj folder, then the gsbserver seems to start but then crashing:

Cannot find a toolchain for EABI: arm64
System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
bei fc..ctor(VisualGDBProjectSettings2 A_0, GDBSessionLaunchOptions A_1, pr A_2, alu A_3, Boolean A_4)
bei VisualGDB.GDBDebugEngine.a(adl A_0)

Regards
Fabian

[Author]

Posts