Andrew Clayton

I think you can simply drop the word "unix". So it's simply `API control socket` The json looks ok to me.

The language modules and versions are handily stored in the `languages` array member of the `nxt_runtime_t` structure... We have access to the following information ```c typedef struct { nxt_app_type_t type;...

I have an initial version that will return something like ```json { "modules": { "python": { "version": "3.12.2", "lib": "/opt/unit/modules/python.unit.so" }, "wasm": { "version": "0.1", "lib": "/opt/unit/modules/wasm.unit.so" }, "wasm-wasi-component": {...

Are you saying you want the JSON formatted differently? Currently it's modelled on the "applications" section ```json "applications": { "luw-echo-request": { "processes": { "running": 1, "starting": 0, "idle": 1 },...

This is of course an entirely _new_ module...

Current work can be found [here](https://github.com/ac000/unit/tree/wasm-wasi-http).

I have an initial [wasi-http](https://gist.github.com/ac000/906707af37b42cdcc9d3cc4c2715da99) version of [luw-echo-request.c](https://github.com/nginx/unit-wasm/blob/main/examples/c/luw-echo-request.c)

I'm going to assume this is on Linux and thus signal 7 is a SIGBUS. If you have a coredump you can try ``` $ gdb /path/to/unitd /path/to/coredump (gdb) bt...

Could you provide a little more details about your environment. What OS? raw metal, vm or container?. Unit config etc...

Thanks! Given that it's getting a `SIGBUS` I'm still inclined to suspect it's being OOM-killed (Out of Memory) rather than an ouright crash due to a SIGSEGV or SIGABRT, but...