How did you guys test GDB? Is it not working even from console using a simple test program?
Its behavior under Lazarus is another issue. There some complex IPC is needed.
However if this is about the issue explained ODROID forum and it can be cured with a recent kernel, then things look good. I will not use time for invertigating it.
I was testing DonAlfredo's Odroid C2 through VNC. You mentioned that building Lazarus "Debug IDE" failed due to lack of memory. How is it possible as Odroid C2 has 2 GB memory? How much of it is used by GPU? How much more memory is needed for 64-bit operation versus 32-bit operation?
Anyway it feels strange. I have built and used Lazarus in a Pentium II machine with 384 MB memory. IIRC the total used memory with swap was below 1 GB at all times.
Some of the problems can come from buggy libraries. I read warnings about it. This ARM 64-bit architechture is new and lots of code is still buggy. I believe things will improve quickly because Odroid C2 and Raspberry Pi 3 have lots of testers.
From an earlier thread:
So I guess reports are NOT welcome in the bug tracker...
Reports about an alpha quality feature are not welcome. There must be some level of stability before reporting bugs makes sense.
For example DonAlfredo's debugger report does not belong to Lazarus bug tracker, it belongs to Odroid bug tracker instead.
Other bugs may be caused by some library, too, nobody knows yet.
One bug report saying "Lazarus is broken on aarch64 systems" would be enough but even that is useless because I knew about it already, and I am the only Lazarus developer who tested the issue after communicating with DonAlfredo.
The same is true with other alpha quality features like GTK3 bindings. A person who wants to improve it does not need bug reports because the missing things are so obvious. Lazarus IDE cannot be built with it for example.