Bug 2031713

Summary:	s390x vgdb tests crash
Product:	Red Hat Enterprise Linux 9	Reporter:	Mark Wielaard <mjw>
Component:	valgrind	Assignee:	Mark Wielaard <mjw>
valgrind sub component:	system-version	QA Contact:	Jesus Checa <jchecahi>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	fche, fweimer, jakub, ohudlick
Version:	9.0	Keywords:	Patch, Triaged
Target Milestone:	rc	Flags:	pm-rhel: mirror+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	valgrind-3.18.1-6.el9	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-17 12:48:06 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 2021-12-13 10:10:12 UTC

Various tests that use vgdb (the valgrind gdb bridge) and signals crash during the regtest run.

gdbserver_tests/nlsigvgdb                (stderr)
gdbserver_tests/nlsigvgdb                (stderrB)
gdbserver_tests/nlvgdbsigqueue           (stderr)
gdbserver_tests/nlvgdbsigqueue           (stdoutB)

The underlying problem is that valgrind doesn't track (unmaps) the vdso.
https://bugs.kde.org/show_bug.cgi?id=444481

There is an upstream patch available that fixes the vdso issue just for s390x (it  still doesn't really expose the vdso to the application, that would be a followup fix).

The fix is already being tested in fedora rawhide valgrind-3.18.1-7.fc36

Comment 1 Jesus Checa 2022-01-03 18:11:58 UTC

Verified that nlsigvgdb and nlsigvgdbqueue tests fail with previous build valgrind-3.18.1-5.el9 but do not anymore with build valgrind-3.18.1-6.el9.

Comment 7 errata-xmlrpc 2022-05-17 12:48:06 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (new packages: valgrind), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:2401