-
Notifications
You must be signed in to change notification settings - Fork 42
Add GDBServer Integration Tests (CI) #162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
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
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:
script/gdbserver_test.cmdand regular expressions.In the future we might want to add tests for other Plugins such as
PrintInstructionor dbusAccess.csv.