Bug 882589

Summary:	dev-cpp/gtest-1.12.1 leaves trace of segfault in dmesg
Product:	Gentoo Linux	Reporter:	Agostino Sarubbo <ago>
Component:	Current packages	Assignee:	Peter Levine <plevine457>
Status:	RESOLVED INVALID
Severity:	normal	CC:	plevine457, proxy-maint
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Agostino Sarubbo gentoo-dev

2022-11-23 07:52:00 UTC

https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/

Issue: dev-cpp/gtest-1.12.1 leaves trace of segfault in dmesg.
Discovered on: amd64 (internal ref: ci)

NOTE:
To reproduce this issue:
1) Install the package with FEATURES=test
2) Check dmesg output with: dmesg -T | grep -E '( segfault | traps:| audit:)'

This type of report comes from a check that is a bit outside of the tinderbox, that's the reason because build.log was not provided (however in cases like these the build.log doesn't help much) but if you need further help to diagnose this issue feel free to ask.

In any case I'm providing what I can see via dmesg.

Comment 1 Agostino Sarubbo gentoo-dev

2022-11-23 07:52:27 UTC

[Wed Nov 23 04:00:15 2022] gtest_repeat_te[36832]: segfault at 7f1fa6c19d48 ip 00007f1fa71fc72f sp 00007f1fa6c19d50 error 6 in libsandbox.so[7f1fa71fb000+c000]
[Wed Nov 23 04:00:15 2022] gtest_repeat_te[36835]: segfault at 7f1fa6c19d48 ip 00007f1fa71fc72f sp 00007f1fa6c19d50 error 6 in libsandbox.so[7f1fa71fb000+c000]
[Wed Nov 23 04:00:15 2022] gtest_repeat_te[36837]: segfault at 7f1fa6c19d48 ip 00007f1fa71fc72f sp 00007f1fa6c19d50 error 6 in libsandbox.so[7f1fa71fb000+c000]
[Wed Nov 23 04:00:15 2022] gtest_repeat_te[36849]: segfault at 7f1fa6c19d48 ip 00007f1fa71fc72f sp 00007f1fa6c19d50 error 6 in libsandbox.so[7f1fa71fb000+c000]
[Wed Nov 23 04:00:15 2022] gtest_repeat_te[36893]: segfault at 7f1fa6c19d48 ip 00007f1fa71fc72f sp 00007f1fa6c19d50 error 6 in libsandbox.so[7f1fa71fb000+c000]
[Wed Nov 23 04:00:15 2022] gtest_repeat_te[36897]: segfault at 7f1fa6c19d48 ip 00007f1fa71fc72f sp 00007f1fa6c19d50 error 6 in libsandbox.so[7f1fa71fb000+c000]
[Wed Nov 23 04:00:15 2022] gtest_repeat_te[36901]: segfault at 7f1fa6c19d48 ip 00007f1fa71fc72f sp 00007f1fa6c19d50 error 6 in libsandbox.so[7f1fa71fb000+c000]
[Wed Nov 23 04:00:15 2022] gtest_repeat_te[36903]: segfault at 7f1fa6c19d48 ip 00007f1fa71fc72f sp 00007f1fa6c19d50 error 6 in libsandbox.so[7f1fa71fb000+c000]
[Wed Nov 23 04:00:15 2022] gtest_repeat_te[36906]: segfault at 7f1fa6c19d48 ip 00007f1fa71fc72f sp 00007f1fa6c19d50 error 6 in libsandbox.so[7f1fa71fb000+c000]
[Wed Nov 23 04:00:15 2022] gtest_repeat_te[36909]: segfault at 7f1fa6c19d48 ip 00007f1fa71fc72f sp 00007f1fa6c19d50 error 6 in libsandbox.so[7f1fa71fb000+c000]

Comment 2 Peter Levine 2022-11-26 19:32:22 UTC

A bit of printk spam about trapped sigsegv signals might seem a bit alarming but it doesn't appear to be a bug, and no test returns a failed state.