<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - SIGSEGV in xkb_context_ref from /usr/lib/libxkbcommon.so.0" href="https://bugs.freedesktop.org/show_bug.cgi?id=94075#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - SIGSEGV in xkb_context_ref from /usr/lib/libxkbcommon.so.0" href="https://bugs.freedesktop.org/show_bug.cgi?id=94075">bug 94075</a> from <a class="email" href="mailto:peter.hutterer@who-t.net" title="Peter Hutterer <peter.hutterer@who-t.net>"> Peter Hutterer</a> <pre>fwiw, I tried reproducing this with 0.5.0 and 0.6.1 (on fedora) and could not get the crash to happen. that's with a count of up to 200 and also with the sleep removed, neither reproduced it here. given the backtrace shows xkb_keymap_new_from_buffer() and the actual failure is in xkb_context_ref() I would assume this is an SDL bug rather than a libxbkcommon bug. The only thing that can segfault here is the ctx argument which is provided by SDL. This indicates that SDL may not initialize the keymap, or that some memory corruption happens, or that the keymap failed to initialize but everything continued as normal valgrind may tell you more</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>