-
Philippe Gerum authored
Pulling memory from the system heap for logging such debug data has two adverse effects: - it might gradually deplete the core heap due to a constantly misbehaving application, - it may leave the user under the (wrong) impression that a memory leak is ongoing in the core heap, when a sane application is restarted multiple times, which invariably causes a few relax spots to be logged during the init phase. We fix this by assigning a private memory pool for this debug feature. Traces will simply stop being logged when the pool is full, until /proc/xenomai/debug/relax is written to for flushing it.
9e0dce83