Mathieu Desnoyers

No, the global-dynamic TLS model won't work, because we require an offset from the thread pointer to be constant across threads, which AFAIK is not guaranteed by global-dynamic.

You are right that the issue is caused by the initial-exec TLS though. Our plan is currently to drop support for rseq registration fallback and just rely on glibc. If...

Executing tests: ./configure make make check We have a few ideas on how to reintroduce the fallback mechanism if need be, and we'd make sure it does not prevent dlopening...

AFAIU, both global and local dynamic TLS end up allocating memory dynamically on first use from each thread (lazy allocation) through execution of a TLS getter function. So the offset...

> Do you know if there are any standalone encoder/decoder implementations of CTF2? We are actively working on the CTF2 source/sink within the Babeltrace project. The ongoing work is being...

> Does barectf support CTF2? I found one [GH issue](https://github.com/efficios/barectf/issues/33) that seems to indicate that the answer is no. As far as the barectf project is concerned, we are very...