Skip to content

gdbserver: honor resume_on_disconnect on last client detach - #2020

Open
jhqian wants to merge 1 commit into
pyocd:mainfrom
jhqian:multiclient-resume-option
Open

gdbserver: honor resume_on_disconnect on last client detach#2020
jhqian wants to merge 1 commit into
pyocd:mainfrom
jhqian:multiclient-resume-option

Conversation

@jhqian

@jhqian jhqian commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

The multi-client gdbserver resumes a halted target when the last GDB client detaches. This resume path did not consult the resume_on_disconnect session option, so the option had no effect on persistent gdbserver sessions where clients detach and reattach. Gate the resume on the option.

The multi-client gdbserver resumes a halted target when the last GDB
client detaches. This resume path did not consult the
resume_on_disconnect session option, so the option had no effect on
persistent gdbserver sessions where clients detach and reattach. Gate
the resume on the option.

Signed-off-by: Ryan QIAN <jianghao.qian@outlook.com>
@jhqian

jhqian commented Aug 21, 2026

Copy link
Copy Markdown
Contributor Author

The "Functional tests Mac" failure is infrastructure: the job was auto-failed with "no enabled agents online to process the request for more than 7 days" — no tests actually ran on macOS.

The 7 reported failed test cases (gdbserver on max32630/nrf51/nrf52833, Linux + Windows) are the long-standing Gdb Test failures that automated_test.py has carried in IGNORE_FAILURE_TESTS since 2021 (c5c33c1, "test: automated_test: ignore failures of connect and gdb tests"). The failure point is the DWT watchpoint exhaustion section, unrelated to the resume_on_disconnect gate added here.

All other functional tests pass on Linux and Windows with this change.

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.

1 participant