Martin Stein fbe9d26c47 trace: initialize trace control in Thread::start ... Previously, the trace control of a thread was initialized in its constructor (which is generic for all components). This has the disadvantage that the CPU-session-pointer member of the thread might not be valid at this point. And it cannot be replaced by using the "deprecated_env" CPU session neither as constructing the deprecated environment in causes troubles in Core. But as the trace control shouldn't be needed in Core anyway, the initialization can be moved to the Thread::start implementation of non-core components. This code already takes care of the CPU session pointer. Fixes #2901		2018-08-02 14:36:35 +02:00
..
cap_map.cc	Adjust file headers to refer to the AGPLv3	2017-02-28 12:59:29 +01:00
capability.cc	Adjust file headers to refer to the AGPLv3	2017-02-28 12:59:29 +01:00
ipc.cc	Adjust file headers to refer to the AGPLv3	2017-02-28 12:59:29 +01:00
region_map_client.cc	base: support to attach RAM dataspaces readonly	2018-05-30 13:36:27 +02:00
rpc_cap_alloc.cc	Capability quota accounting and trading	2017-05-31 13:16:06 +02:00
rpc_entrypoint.cc	base: safeguard entrypoint against double manage	2017-05-31 13:16:05 +02:00
signal_transmitter.cc	base: restructure signal-submit initialization	2017-05-31 13:16:12 +02:00
sleep.cc	Follow practices suggested by "Effective C++"	2018-01-17 12:14:35 +01:00
stack_area_addr.cc	base: make stack area base specifiable for core	2017-08-28 16:49:46 +02:00
stack.cc	AVL node/tree: make non-copyable	2018-02-09 13:34:23 +01:00
thread_start.cc	trace: initialize trace control in Thread::start	2018-08-02 14:36:35 +02:00