Replies: 1 comment
-
Seems like some of the syscalls gdb needs to debug processes doesn't work under qemu + rosetta and so this is just another M1 issue. Created an ARM Linux machine and debugging worked out of the box. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Currently I'm trying to debug a program in Rust where I'm using VSCode remote feature so its connecting to a Linux machine over SSH and building it there and then attaching and debugging. The launch configuration looks like this:
Settings:
After it launches in the debug console I can see it is doing some stuff:
Here is the whole
debug_info show
: https://gist.github.com/sontek/afab76787e23304c7ca2a6f2b1f65865The binary that got built does seem to have debug symbols:
Here is some of the CodeLLDB log output:
https://gist.github.com/sontek/e32d0f8c3f5b568044b123164e1a8ee1
I've also tried adding panic in the code and it doesn't break for that either. There are breakpoints in lldb:
Beta Was this translation helpful? Give feedback.
All reactions