Apple M1 ARM support

[luminacious]

Hi All

Hope you're all safe and well.

You're probably already aware of this but just in case.

When trying to debug on Apple M1, it comes back with "rosetta error: failed to allocate vm space for aot".

Just wondering if there's any recommendations please.

Love your work 😊👍

[aarzilli]

Go doesn't officially support darwin/arm64 until go1.16, delve won't ufficially support go1.16 until 1.6.0, we don't have access to darwin/arm64 machines to port delve to them so support for delve on darwin/arm64 is unplanned. It's highly unlikely that debuggers can work through rosetta.

[oxisto]

I have started with a darwin-arm64 branch on my fork here. https://github.com/oxisto/delve/tree/darwin-arm64

I basically just started this a couple of hours ago. The native code seems to compile (I am pretty sure it is not functional yet), but Go still throws some link errors. I am not too familiar with that kind of low level programming, so I need some more prep time to fully understand all of it.

Beware, you need a recent Go version that can compile darwin/arm64, i.e. installed using go tip.

Update : Ah, looks like I was going down the wrong route using the native backend. I think I might need to have a better understanding of delve first, I will continue with this tomorrow.

[aarzilli]

The native code has always had problems, the backend that's being used by default is in pkg/proc/gdbserial, I would focus on that.

[oxisto]

The native code has always had problems, the backend that's being used by default is in pkg/proc/gdbserial, I would focus on that.

Thanks for the pointer in the right direction. I have begun working in this direction on a second fork (https://github.com/oxisto/delve/tree/darwin-arm64-lldb) just by duplicating code for the gdbserver for arm64 now. Spawning an executable works but setting a breakpoint already crashes. I will continue working in this direction then. I will also apply for the mailing list, as you would like to move the discussion there and not on the GitHub issues if I have seen the guidelines correctly.

[eoarch]

Is is possible to test a fork/version currently, or is this issue still awaiting other changes? (:

[andig]

I'm still seeing these errors on Go 1.16:

API server listening at: 127.0.0.1:3694
rosetta error: failed to allocate vm space for aot
Failed to continue - protocol error E74 during registers read for packet $g;thread:88fee;
Last known immediate stacktrace (goroutine id 0):
    ?:-1
        <unknown>
    :0
        <unknown>

Should I open a go ticket?

[s0xzwasd]

@andig pay attention that you go version should be 1.16 darwin/arm64 instead of 1.16 darwin/amd64.

[dragonly]

I installed go with go version go1.16 darwin/arm64, and delve 1.6.0, and setup to debug TiDB. which starts fine, but prints wrong var values, and the n command behave like drunk 😦

btw, I run dlv exec bin/tidb-server and break server/conn.go:953, then connect with mysql -uroot -P 4000 -h 127.0.0.1. the cmd variable should have value 3 which means query command in mysql protocol, but it shows 200. Running on amd64 platform and it is correct.

and the next command will lead me to arbitrary line, which is not useful.