@dbaeumer I just realized this morning that we may have a miscommunication on the repo for this. Thought I'd just put this up to show it, while I work on moving this to the other repository.

Currently we can only plug-in filesystems on the VS Code side. To get pdb debugging work it would be helpful to support having a pluggable device driver on the WSAM-WASI side as well. This would allow to have special character devices to communicate with pdb.

Suppose you have something like so:

Main Thread - Extension code Worker 1 - Extension sub piece, which starts Worker 2 Worker 2 - Needs to use the sync api

Worker 2 cannot communicate with the Main Thread because its MessageChannel is only with Worker 1.

For CPython I have this exact situation when trying to run the debugger:

• Main thread - Extension code
• Worker 1 - Load of python.js
• Worker 2 - Reader thread for debugger
• Worker 3 - Writer thread for debugger

Worker 2 and 3 cannot send messages to the Main Thread.

• Note: Emscripten (by default proxies) all FS (or socket) API calls to its main thread (worker 1 in this case) but that causes deadlock issues because the Atomics.wait in the sync-api block the main worker thread, therefore no other fs API calls can be handled while waiting. Took me a while to figure this out as most of it was working until Worker 3 tried to acquire a lock.

We need to come up with a testing strategy for the WASI implementation. Ideas:

• implement tests in TS and call the implementation methods directly
• implement tests in Rust/C++ and compile them to WASM-WASI and execute them through the web assembly execution.