Going on with my tests, those errors seems "interleaving" problems, where one thread writes to stderr while another is writing, most of the times you can see the "interrupted" line continuing after the interleaved one.
This should not happen, since fprintf should be atomic according to glibc, but this goes out of my reach.
I've tested rebuilding my container with rocky 9 and voilà, problem fixes. So is definitely something related to glibc/gcc differences between noble and rocky.
Now I'm gonna test it with debian bookworm and see what happens.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4203/2808805812@github.com>
Going on with my tests, those errors seems "interleaving" problems, where one thread writes to stderr while another is writing, most of the times you can see the "interrupted" line continuing after the interleaved one.
This should not happen, since fprintf should be atomic according to glibc, but this goes out of my reach.
I've tested rebuilding my container with rocky 9 and voilà, problem fixes. So is definitely something related to glibc/gcc differences between noble and rocky.
Now I'm gonna test it with debian bookworm and see what happens.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <kamailio/kamailio/issues/4203/2808805812@github.com>
xadhoom left a comment