Skip to content

Conversation

@PhilippvK
Copy link
Member

In preparation to merging #161, I wanted to add some gdbserver-related smoke tests to our ci.

Before this can be merged a few TODOs need to be resolved:

  • Support building examples using Clang/LLVM
  • Support debugging with lldb
  • Improve script/gdbserver_test.cmd and regular expressions.

In the future we might want to add tests for other Plugins such as PrintInstruction or dbusAccess.csv.

@PhilippvK PhilippvK self-assigned this Aug 23, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Apologies for tardy feedback; wanted toi run this against a working seal5 LLDB and with current pyenv config getting a properly patched build without a broken libpython dependency stalled the task (finally bypassed with LLDB_ENABLE_PYTHON: false in llvm.yml). Here's the simplest set of LLDB equivalents - note that the GDB command aliases are only for the short forms, eg "b" works but not "break". These aliases are built-in and I imagine stable, but the native equivalents for "bt" and "b" are "thread backtrace" and "breakpoint set -name" (rational, orthogonal, but too verbose)

gdb-remote 2001
bt
register read
b main
b _exit
continue
bt
register read
continue
bt
register read
register read x0
register read zero
register read pc

@PhilippvK PhilippvK added this to the Release v0.12 milestone Sep 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants