gdbclient: Read thread uid, gid and status from procfs

[SELESTER11]

Your checklist for this pull request

• I've read the guidelines for contributing to this repository.
• I made sure to follow the project's coding style.
• I've documented every RZ_API function and struct this PR changes.
• I've added tests that prove my changes are effective (required for changes to RZ_API).
• I've updated the Rizin book with the relevant information (if needed).
• I've used AI tools to generate fully or partially these code changes and I'm sure the changes are not copyrighted by somebody else.

Detailed description

gdbr_threads_list was hardcoding uid, gid and status to -1 and RZ_DBG_PROC_STOP. I noticed gdbr_parse_processes_xml already does this for processes by reading /proc/<pid>/status over vFile, so I did the same for threads using /proc/<pid>/task/<tid>/status. Falls back to defaults if the remote doesn't support vFile or isn't Linux.

Test plan

This change requires a Linux gdbserver with a multi-threaded binary and vFile support to verify. Open to suggestions on how to add a test for this.

Closing issues

N/A

[SELESTER11]

@wargio Could you approve the CI workflows when you get a chance? Keeping the PR as draft until CI passes.

[codecov]

Codecov Report

❌ Patch coverage is 0% with 27 lines in your changes missing coverage. Please review.
✅ Project coverage is 48.39%. Comparing base (519cef5) to head (30176a0).
⚠️ Report is 31 commits behind head on dev.

Files with missing lines	Patch %	Lines
subprojects/rzgdb/src/gdbclient/core.c	0.00%	27 Missing ⚠️

Additional details and impacted files

Files with missing lines	Coverage Δ
subprojects/rzgdb/src/gdbclient/core.c	26.47% <0.00%> (-0.54%)	⬇️

... and 7 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 519cef5...30176a0. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[notxvilka]

Good idea but more work is needed

[vkaramchanda]

@notxvilka I've addressed all the feedback. Could you re-review and mark this ready for review when you get a chance?

[SELESTER11]

The char buffer caused a -Wpointer-sign error when passed to gdbr_read_file(ut8 *buf). Added (ut8 *) cast at the call site, matching how gdbr_parse_processes_xml does it in xml.c.

[wargio]

use \ instead of @

[SELESTER11]

Done, switched to \brief.

[SELESTER11]

@notxvilka All three of your feedback points have been addressed. Could you re-review when you get a chance?

[Rot127]

Please add a test

[SELESTER11]

Please add a test

@Rot127 Happy to add a test. This change requires a Linux gdbserver with a multi-threaded binary and vFile support to verify. Could you point me to existing test infrastructure I should follow, or suggest a pattern for testing gdbserver-dependent functionality?

[Rot127]

There are already tests which use a gdb server in test/db/archos/linux-x64/dbg_gdbserver.
Please check those for examples.

For the binary: You can check the existing rizin-testbins repo for one.
But I think it is easier to just vibe code a tiny program, compile it and upload the binary + source code to the rizin-testbins repo.

[SELESTER11]

There are already tests which use a gdb server in test/db/archos/linux-x64/dbg_gdbserver. Please check those for examples.

For the binary: You can check the existing rizin-testbins repo for one. But I think it is easier to just vibe code a tiny program, compile it and upload the binary + source code to the rizin-testbins repo.

Done, added test in test/db/archos/linux-x64/dbg_gdbserver. Binary + source in rizinorg/rizin-testbins#287.

[Rot127]

Merged it, please rebase

[Rot127]

Please fix the tests.

[Rot127]

Can the output of the test be more descriptive?
Just a * and - has no meaning.

[SELESTER11]

Fixed -- changed EOF2 to EOF (parser only accepts EOF) and updated the expected output to show the status character for each thread (* t and - t), which is more descriptive.