… (the true) creation of the underlying buffer.

Initialization of an already intialized mutex or condition variable may result in undefined behavior. In the context of multiple users one 'creates' and others 'open'. This allows differentiation similar to the contructor taking DataElementFile as argument.

…ition variables are properly initialized before first use.

The typical use case is inter-process, but it allows for multiple threads within a process as gettid() is unique over all processes.

…ond_wait' and 'pthread_cond_timedwait'.

Different workers may be executed from the same underlying pthread.

…to avoid deadlocks.

…ble (underlying) buffer sizes.

…size.

Check 'length == 0' only once.

…0c1e9c3cfa' from 'development/cyclicbuffer-deadlock-on-length'.

…14546c50' from 'development/cyclicbuffer-deadlock-on-length'.

Although explicit specification may be preferred, implicit is apparently the accepted use case.

…df7d2259'.

While (looped) waiting on condition variable in 'Sync()' the time out triggers an 'abort()'.

…ildren.

…finite'.'

…ader(s).

…042a5c63'.

In addition: 'initiator' is only relevant for valid buffers.

Multiple 'writers' can try to make a reservation in a guarded state. There is no option to check beforehand and they should check the return value. In addition, the return value is ambiguous as error codes are masked by 'actuallength'.

'writers' have no ability to check the presense of any ongoing reservation.

… head.

Custom lengths should consider (maximum) distance between tail and head.

…bd'.

- Unresponsive child processes are 'killed' after a set timeout.

- Disable ASSERT triggers in 'test_cyclicbuffer'

It is unintuitive that the anmount of data is always 1 less than the (maximum) size.

The condition prevents checking an invalid state after construction. Moreover, the invalid state condition is part of the return value, and, identical ASSERTs are used throughout the code where the invalid pointer may be used.

Kept certain 'local' files intact with merge strategy

…buffer_dataexchange'.

…1af07068533d5035e434137863df792cc'

…23'.

- Start using the unresponsive detection.

- Copy and use the boolean result of the guarded code.

- Added or modified comments.

- Only validate reader data if overwrite is disabled.

…testing the effect of 'Reserved' and 'Write'

Make more explicit the effect of 'write', 'reserved' and 'overwrite' with modified data set

…buffer_dataexchange.cpp'.

… and revert 'CyclicBuffer' changes

* Added buildinfo method for QA report

* Added public compilesettings

* Updated Controller.cpp from seb comments

* Updated CMakeLists.txt in core

* added priv compilesettings

* Added threadcount to buildinfo

* Added unused variable macro

* systemtype and universal build flags

* enum extensions

* spelling

* empty commit to test action

* shortened namespaces and whitespace

* extra line

---------

Co-authored-by: Pierre Wielders <pierre@wielders.net>

…cbuffer'

…taexchange'