Issue 153377
Summary [lldb] Remote debugging from Linux to macOS shows `<invalid type>` for registers
Labels new issue
Assignees
Reporter patryk4815
    ### Repro:
Bug only happening between linux + macOS.

#### Run this on linux:
```console
$ lldb-server g 0:1234 ./hello.arm64
```

#### Run this on macOS:
```console
$ lldb
(lldb) platform select remote-gdb-server
  Platform: remote-gdb-server
 Connected: no
(lldb) process connect --plugin gdb-remote connect://0:1234
Process 789135 stopped
* thread #1, name = 'hello.arm64', stop reason = signal SIGSTOP
    frame #0: 0x000000000101acd0
->  0x101acd0: mov    x29, #0x0 ; =0
    0x101acd4: mov    x30, #0x0 ; =0
    0x101acd8: mov    x0, sp
 0x101acdc: adrp   x1, -4122
(lldb) script
Python Interactive Interpreter. To exit, type 'quit()', 'exit()' or Ctrl-D.
>>> lldb.frame.GetRegisters().GetValueAtIndex(0).GetChildMemberWithName('pc')
pc = 0x000000000101acd0 <invalid type>
>>>
```
> register type is `<invalid type>`, this is not happening on linux

### Expected behavior
Registers should have valid `type`
```
>>> lldb.frame.GetRegisters().GetValueAtIndex(0).GetChildMemberWithName('pc')
(unsigned long) pc = 0x000000000101acd0
```


### My env:
- lldb version 20.1.6
- Apple M4 Pro
- Linux arm64 vm on macOS

_______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

Reply via email to