Bug 560614

Summary:	Add check of config.log for "Segmentation fault" errors in QA checks list
Product:	Portage Development	Reporter:	Sergey S. Starikoff <Ikonta>
Component:	Core - Ebuild Support	Assignee:	Portage team <dev-portage>
Status:	UNCONFIRMED ---
Severity:	enhancement	CC:	beelzebubbie.logs, qa, sam
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
See Also:	https://bugs.gentoo.org/show_bug.cgi?id=504760
Whiteboard:
Package list:		Runtime testing required:	---

Description Sergey S. Starikoff 2015-09-16 10:12:23 UTC

Portage provides very useful feature: automatical QA checks.

Working on pretty hidden bug #504760 (to verify it user must set FEATURES="keepwork" and read config.logs (do you believe in it?) or enable writing core dumps into _dedicated_ directory) and getting yesterday this issue for some other package (according to times of files and build times in emerge.log it seemed to be =gnome-base/dconf-0.24.0, but today I've failed to reproduce it) I've thought, that it will be fine, if portage itself will inspect build system's logs (i.e. config.log) on such issue, reporting errors in QA message.
This will allow to include in debugging all those, who uses Linux default (writing core dumps is disabled on kernel level).

Example of error message:
config.log:
…
configure:8037: ./conftest
./configure: line 2121: 24105 Segmentation fault      (core dumped) ./conftest$ac_exeext
…

Comment 1 Sergey S. Starikoff 2016-05-24 08:54:51 UTC

For now (sys-devel/gcc-4.9.3 and sys-libs/glibc-2.22-r4) I've got the same issue with =net-ftp/lftp-4.7.1 (reproduced with =net-ftp/lftp-4.7.2).
Is it sufficient to report such issues upstream, or bgo reports also needed?