------- Comment on attachment From s...@de.ibm.com 2024-07-17 07:13 EDT-------
(In reply to comment #5) > Hello and thanks for having reported this, actually shared this with us. > > Is there a simple reproducer or test case that could be used to provoke the > segfault and with that to verify that it got fixed with the commit included? Florian Weimer has listed the single case which results in the segfault here: Bug 31934 - wcsncmp crash on s390x on vlbb instruction https://sourceware.org/bugzilla/show_bug.cgi?id=31934#c0 This was extracted from his full-tests here: [PATCH] manual: Document a GNU extension for strncmp/wcsncmp <https://inbox.sourceware.org/libc-alpha/87r0cipcps....@igel.home/> The attached file is a standalone version of this wcsncmp test which does not rely on the glibc-internals. It just calls wcsncmp. ** Bug watch added: Sourceware.org Bugzilla #31934 https://sourceware.org/bugzilla/show_bug.cgi?id=31934 ** Attachment added: "Standalone test" https://bugs.launchpad.net/bugs/2073372/+attachment/5798051/+files/tst-bz31934-wcsncmp-standalone.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073372 Title: [UBUNTU 20.04] s390x: z13 wcsncmp implementation segfaults if n=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2073372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
