Bug 1658677 - Fix sigkill.stderr.exp for glibc-2.28
Summary: Fix sigkill.stderr.exp for glibc-2.28
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: valgrind
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Mark Wielaard
QA Contact: Alexandra Petlanová Hájková
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-12 16:22 UTC by Mark Wielaard
Modified: 2019-06-14 01:29 UTC (History)
3 users (show)

Fixed In Version: valgrind-3.14.0-6.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-14 01:29:03 UTC
Type: Bug
Target Upstream Version:


Attachments (Terms of Use)

Description Mark Wielaard 2018-12-12 16:22:53 UTC
glibc 2.28 filters out some bad signal numbers and returns
Invalid argument instead of passing such bad signal numbers
to the kernel sigaction syscall. So valgrind won't see such 
bad signal numbers and won't print "bad signal number".

Upstream commit 0c701ba2a4b10a5f6f3fae31cb0ec6ca034d51d9
fixes this and makes the existing memcheck/tests/sigkill
regtest PASS.


Note You need to log in before you can comment on or make changes to this bug.