Skip to content

0.24.0 and 0.24.1: a start bounded by the kernel alone; what an observation of a unit answers (openkal 0.26); a request acted on by another context ends the program as the request - #52

Open
Sunrisepeak wants to merge 2 commits into
mainfrom
openkal-0.26.0
Open

Sunrisepeak wants to merge 2 commits into
mainfrom
openkal-0.26.0

Conversation

@Sunrisepeak

@Sunrisepeak Sunrisepeak commented Nov 19, 2026 •

Copy link
Copy Markdown
Member

Part of the round recorded in mcpp-community/mcpp .agents/docs/2026-11-19-ecosystem-rule-convergence-design.md (sections 9 and 10.3 A; mcpp#958, mcpp#952). The branch openkal-0.26.0 is the same name in every repository of the family; the description is completed before merge.

0.24.1 (commit 8a6c4c4, tag 0.24.1): a request acted on by a context other than the program's first ends the program as the request. kal_process_end_as_requested waits up to a tenth of a second for the delivery, as openkal-linux does, before the exit with 128 + the signal. Measured with the new case of tests/stop_word_and_sigpipe.cpp (twenty copies whose second context acts on the request): 9 of 20 end by SIGTERM under the 0.24.0 implementation (probe #54), 20 of 20 under 0.24.1. Found through okrun 0.7.0, whose own context acts on the request (mcpplibs/openkal-image#43).

… unit answers (openkal 0.26)

- the bound of 512 entries upon an argument vector and an environment is
  removed; E2BIG is kal_err_no_space, where it was kal_err_io (clause 7.6)
- a reference of another boot session is EMPTY, where open refused it; one
  whose number a program of another start now holds is EMPTY, where it was
  UNKNOWN (clause 7.18)
- KAL_PROCESS_PROP_JOB_OBSERVE is claimed only where a reference can be made
- openkal ^0.26.0
… request

kal_process_end_as_requested restores the request's default treatment,
unblocks it and sends it to the program again; a program still there a
moment later ends with the status a shell gives one so ended. The kernel
gives a signal sent to the program to the first of its contexts that does
not block it, which need not be the caller, and the moment was not waited
for: called from a context other than the first, kill returned before the
signal was delivered and the exit ended the program first, so its starter
saw 143 where the request's own end was SIGTERM (okrun 0.7.0, whose own
context acts on the request, on the macos-15 arm64 runners). The call now
waits up to a tenth of a second for the delivery, as openkal-linux does.

Test: tests/stop_word_and_sigpipe.cpp runs twenty copies whose second
context acts on the request while the first waits for it; each ends by
SIGTERM.
@Sunrisepeak Sunrisepeak changed the title 0.24.0: a start bounded by the kernel alone; what an observation of a unit answers (openkal 0.26) 0.24.0 and 0.24.1: a start bounded by the kernel alone; what an observation of a unit answers (openkal 0.26); a request acted on by another context ends the program as the request Nov 19, 2026
Sunrisepeak added a commit to mcpplibs/openkal-platform that referenced this pull request Nov 20, 2026
…nd as the image makes it and an image an image starts (#40)

A patch of the version group with two members; no other member changes, and the platform requires mcpp 2026.11.17.1, as 0.31.0 does.

- **openkal-image 0.7.1** (the carrier `openkal-run`, the tools `okld`, `okrun`, `okprof`, and the build dependency `openkal-tools`; mcpplibs/openkal-image#43). An image file or an okb that an image starts is entered through the loader the runner names, held to the runner's signature requirements, with the vector its starter gave, and the image's name is absolute (mcpplibs/openkal-image#42); under 0.7.0 the start ended by SIGSEGV on Linux. The runner takes the requests to end once the image is loaded, and its task that waits for them returns before the program ends: GDB 15, continued to the end, sees the program end as the image ended it (under 0.7.0 it stopped with "Couldn't get registers: No such process").
- **openkal-macos 0.24.1** (mcpplibs/openkal-macos#52, #54). A request acted on by a context other than the program's first ends the program as the request. The runner's task is such a context; under 0.24.0 the program's exit came before the request's own delivery, and of twenty copies nine ended by the request and eleven with status 143.

Both members are in the published index (mcpplibs/mcpp-index#849, #850). Under mcpp 2026.11.19.1 a range request for a member of a version group resolves to the group's version (mcpp-community/mcpp#956), so projects that name 0.31.0 keep openkal-macos 0.24.0.
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