genode/repos/os
Stefan Kalkowski b585583ec7 core: do not destroy in object pool's apply scope
Destroying an object within the scope of a lambda/functor executed
in the object pool's apply function leads potentially to memory corruption.
Within the scope the corresponding object is locked and unlocked when
leaving the scope. Therefore, it is illegal to free the object's memory meanwhile.
This commit eliminates several places in core that destroyed wrongly in
the object pool's scope.

Fix #1713
2015-09-30 12:20:40 +02:00
..
doc init: propagate exit conditions of children 2015-09-30 12:20:36 +02:00
include safeguard the synchronized allocator template 2015-09-30 12:20:39 +02:00
lib/mk Introduce 'spec' subdirectories to outline aspects 2015-09-16 13:58:50 +02:00
run Introduce 'spec' subdirectories to outline aspects 2015-09-16 13:58:50 +02:00
src core: do not destroy in object pool's apply scope 2015-09-30 12:20:40 +02:00
README os: remove dde_kit 2015-06-22 14:43:34 +02:00

This is the example operating system based on the Genode OS framework:

:_Init_: is the first real process in the system. The provided implementation
  uses a very simple XML parser to read its configuration files.

:_Drivers_: The example OS has basic drivers for frame buffer, mouse and
  keyboard input, the PCI bus, the real-time clock, and system-specific timers.

:_Server_: The only server in the example OS is Nitpicker, a
  minimal-complexity GUI server.

:_Test_: are also part of the example OS. You may have a look at the fork
  bomb as a simple system stress test.

:_Ldso_: is the dynamic linker used for loading executables that are linked
  against shared libraries.

:_Lib_: contains libraries used by the components of the OS repository,
  for example, the alarm framework.