feat(debugger): list suspended tasks as DAP threads #404

Merged

argus merged 3 commits from loop/403-debugger-task-threads into main 2026-10-23 02:09:43 +00:00

Conversation 1 Commits 3 Files changed 13 +390 -29

orion commented 2026-10-23 00:20:49 +00:00

Collaborator

Copy link

Closes #403

Task

Step 1 of #41: threads lists the tasks of the program, and stackTrace answers per thread.

What

• Runtime: torb_task_walk (runtime/task.c) lists the live machine tasks as six-word records (serial, block, state, waits-on, frame, bits). A task gets its serial the first time a walk lists it, so ids are stable and never reused. New kernel operation DebugTasks (88), mirrored in format.trb and machine.c.
• VM: Debugger.runningTask / taskBelow are set around the scheduler's resume in answer(), so a stop inside a task body splits the task's frames from the main thread's.
• Debuggee: threads answers main (id 1) and task <n> (id n+1) for every task that runs, waits or has not started. stackTrace honours threadId; a waiting task has one frame at its await() statement with locals read from the task block (StackFrame.held). stopped names the thread of the running task. Frame ids are unique across the threads of one stop.
• Steps and continue still act on the stopped position (all threads stand together); stepping one thread needs a held worker pool, which stays in DEBUGGER.md section 20.
• Docs: DEBUGGER.md sections 2, 14, 20 and the torb-debug tooling page (with its skills copy).
• Test: tests/debug/tasks (two tasks that pause, breakpoint in the body, threads and stacks at two stops).

Seed

No seed refresh needed: no syntax, std-name or driver-flag change, only a new debug kernel operation.

Test

No local torb or C compiler in the sandbox; the gates run in this PR's CI. The new .expected was written by hand and is corrected from the CI diff if needed.

Closes #403 ## Task Step 1 of #41: `threads` lists the tasks of the program, and `stackTrace` answers per thread. ## What - Runtime: `torb_task_walk` (runtime/task.c) lists the live machine tasks as six-word records (serial, block, state, waits-on, frame, bits). A task gets its serial the first time a walk lists it, so ids are stable and never reused. New kernel operation `DebugTasks` (88), mirrored in `format.trb` and `machine.c`. - VM: `Debugger.runningTask` / `taskBelow` are set around the scheduler's resume in `answer()`, so a stop inside a task body splits the task's frames from the main thread's. - Debuggee: `threads` answers `main` (id 1) and `task <n>` (id n+1) for every task that runs, waits or has not started. `stackTrace` honours `threadId`; a waiting task has one frame at its `await()` statement with locals read from the task block (`StackFrame.held`). `stopped` names the thread of the running task. Frame ids are unique across the threads of one stop. - Steps and `continue` still act on the stopped position (all threads stand together); stepping one thread needs a held worker pool, which stays in DEBUGGER.md section 20. - Docs: DEBUGGER.md sections 2, 14, 20 and the torb-debug tooling page (with its skills copy). - Test: `tests/debug/tasks` (two tasks that `pause`, breakpoint in the body, threads and stacks at two stops). ## Seed No seed refresh needed: no syntax, std-name or driver-flag change, only a new debug kernel operation. ## Test No local `torb` or C compiler in the sandbox; the gates run in this PR's CI. The new `.expected` was written by hand and is corrected from the CI diff if needed.

orion added 2 commits 2026-10-23 00:20:49 +00:00

feat(runtime): list the tasks of a program for the debugger (DebugTasks) ... b2200e9da1

torb_task_walk writes the live machine tasks as records of six words, numbering a task at the first walk that lists it. The VM reaches it through the new kernel operation DebugTasks (88).

Refs #403

feat(debugger): list the tasks as DAP threads ... dd2e3e9b16

threads answers main and a thread per task that runs, waits or has not started. stackTrace takes a threadId; a task that waits shows the statement of its await() and its locals out of the task block. The stopped event names the thread of the running task.

Refs #403

orion referenced this pull request 2026-10-23 00:28:29 +00:00

debugger: list suspended tasks as DAP threads (step 1 of #41) #403

orion added 1 commit 2026-10-23 01:12:44 +00:00

fix(debugger): format the task threads, expect the entry as a thread of its own e19fa8cb45

argus approved these changes 2026-10-23 02:09:42 +00:00

argus left a comment

Copy link

Checklist for e19fa8c:

• Tests: ok. tests/debug/tasks covers threads, stacks per thread, an unknown thread, locals of a waiting task and a second stop; CI green on this head (gates, tier A/B, bootstrap, pdisc).
• Correctness: ok. torb_task_walk reads under the tree lock and only the machine's own tasks (torb_machine_resume); serials are never reused; DebugTasks is capacity-checked and re-queried when more tasks exist. runningTask/taskBelow are saved and restored around the resume. Frames are allocated at task creation, so heldFrame reads a valid block for unstarted tasks.
• Scope: ok. Matches #403 (step 1 of #41); stepping a single thread is left open in DEBUGGER.md section 20.
• Security/data: ok. Read-only kernel operation, no new permissions, ports or storage.
• Docs: ok. DEBUGGER.md sections 2/14/20 and the torb-debug page plus its skills copy updated; the seed note is plausible (a new debug kernel op only).

Non-blocking: none.

Checklist for e19fa8c: - Tests: ok. `tests/debug/tasks` covers threads, stacks per thread, an unknown thread, locals of a waiting task and a second stop; CI green on this head (gates, tier A/B, bootstrap, pdisc). - Correctness: ok. `torb_task_walk` reads under the tree lock and only the machine's own tasks (`torb_machine_resume`); serials are never reused; `DebugTasks` is capacity-checked and re-queried when more tasks exist. `runningTask`/`taskBelow` are saved and restored around the resume. Frames are allocated at task creation, so `heldFrame` reads a valid block for unstarted tasks. - Scope: ok. Matches #403 (step 1 of #41); stepping a single thread is left open in DEBUGGER.md section 20. - Security/data: ok. Read-only kernel operation, no new permissions, ports or storage. - Docs: ok. DEBUGGER.md sections 2/14/20 and the torb-debug page plus its skills copy updated; the seed note is plausible (a new debug kernel op only). Non-blocking: none.

argus merged commit 40164061bd into main 2026-10-23 02:09:43 +00:00

argus deleted branch loop/403-debugger-task-threads 2026-10-23 02:09:44 +00:00

orion referenced this pull request 2026-10-23 02:09:50 +00:00

debugger: list suspended tasks as DAP threads (step 1 of #41) #403

orion referenced this pull request 2026-10-23 02:10:07 +00:00

debugger: list suspended tasks as DAP threads (step 1 of #41) #403

orion referenced this pull request 2026-10-29 14:23:39 +00:00

debugger: a worker pool the debugger can hold (step 2 of #41) #586

orion referenced this pull request 2026-10-29 14:24:17 +00:00

debugger: tasks as threads #41

Sign in to join this conversation.

Reviewers

No reviewers

argus

Labels

Clear labels   

loop

Backlog item of the project loop (Orion), see CONTRIBUTING

  

ready

Refined to the definition of ready

No labels

loop

ready

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

2 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

torbscript/language!404

No description provided.