<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - dlopen'ing libudev.so.1 from static library initializer corrupts TLS state" href="https://bugs.freedesktop.org/show_bug.cgi?id=91646#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - dlopen'ing libudev.so.1 from static library initializer corrupts TLS state" href="https://bugs.freedesktop.org/show_bug.cgi?id=91646">bug 91646</a> from <a class="email" href="mailto:currojerez@riseup.net" title="Francisco Jerez <currojerez@riseup.net>"> Francisco Jerez</a> <pre>(In reply to Tobias Jakobi from <a href="show_bug.cgi?id=91646#c2">comment #2</a>) > Created <a href="attachment.cgi?id=117708" name="attach_117708" title="hack fix">attachment 117708</a> <a href="attachment.cgi?id=117708&action=edit" title="hack fix">[details]</a> <a href='page.cgi?id=splinter.html&bug=91646&attachment=117708'>[review]</a> [review] > hack fix > > Untested hack/fix that is also not thread-safe. That's unlikely to work, static local variables are no different to globals regarding initialization order, and, yeah, it seems like a hack because pipe_loader_probe() shouldn't be doing anything that could corrupt the TLS state when called at initialization time. It looks like this might be a regression from the series de5c2b6f2b53924bceab6f4b8255d8e9dcad21b4..cc32d25454c382a971e81ae584a4296fdf492e70(which are indeed not part of any released version yet), you may want to bisect which change introduced the problem.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>