Bug 1658677

Summary:	Fix sigkill.stderr.exp for glibc-2.28
Product:	Red Hat Enterprise Linux 8	Reporter:	Mark Wielaard <mjw>
Component:	valgrind	Assignee:	Mark Wielaard <mjw>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Alexandra Petlanová Hájková <ahajkova>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.0	CC:	ahajkova, jakub, ohudlick
Target Milestone:	rc
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	valgrind-3.14.0-6.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-14 01:29:03 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.