8e7aa54493
For asynchronously provided sessions, the parent has to maintain the session state as long as the server hasn't explicitly responded to a close request. For this reason, the lifetime of such session states is bound to the server, not the client. When the server responds to a close request, the session state gets freed. The 'session_response' implementation does not immediately destroy the session state but delegates the destruction to a client-side callback, which thereby also notifies the client. However, the code did not consider the case where the client has completely vanished at session-response time. In this case, we need to drop the session state immediately. Fixes #2391 |
||
|---|---|---|
| .. | ||
| etc | ||
| include | ||
| lib | ||
| mk | ||
| run | ||
| src | ||
| README | ||
This is generic part of the Genode implementation. It consists of two parts: :_Core_: is the ultimate root of the Genode application tree and provides abstractions for the lowest-level hardware resources such as RAM, ROM, CPU, and generic device access. All generic parts of Core can be found here - for system-specific implementations refer to the appropriate 'base-<system>' directory. :_Base libraries and protocols_: that are used by each Genode component to interact with other components. This is the glue that holds everything together.