Dear Kernel hackers, We're having an interesting case that needs urgent diagnosis in Factory (as it's a ring-1 package, it blocks anything else from entering, as the staging areas all show the same issue). The issue: libsigsegv fails the test suite since the kernel has been updated to 3.18.3 (before we had 3.18.1). The test suite is intentionally 'badly written' and is supposed to cause sigsegv for various cases. The current tests failing are around stack overflows. Up to kernel 3.18.1, those reported SIGSEGV back, but it seems nowadays we get a SIGBUS (which is not in scope of a library called libSIGSEGV to be caught). Are you aware of or can think of any change in the kernel that would cause this to happen? Or is the error the stackoverflow sample tries to catch, simply no longer meant to be caught by a sigsegv? One of the tests failing is the code to be found at http://git.savannah.gnu.org/cgit/libsigsegv.git/tree/tests/stackoverflow1.c Thanks a lot for your help! Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org