When a portion of the sliced heap gets freed, the corresponding block gets removed from the list of blocks, and it's dataspace containing the block gets detached, but it's destructor never gets called. This leads to leaking capabilities, when Native_capability is implemented as smart-pointer, because the destructor of Ram_dataspace_capability that is part of the Block object gets never called. |
||
---|---|---|
.. | ||
base | ||
core | ||
lib | ||
platform | ||
test | ||
README |
This directory contains all source codes.