RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Bug 1473411 - gdb leaks ignored SIGPIPE to child process - fix has caused a regression when one tried to LD_PRELOAD=/lib64/libSegFault.so for GDB itself.
While it IMO does not make too much sense to run it for GDB it is common for people to incorrectly LD_PRELOAD libraries already to GDB despite they want to preload them for the program being debugged (and they should use -ex 'set env LD_PRELOAD=/lib64/libSegFault.so' instead). So I believe the regression can happen in practice.

Version-Release number of selected component (if applicable):
PASS: RHEL-7.4 or gdb-7.6.1-106.el7
FAIL: gdb-7.6.1-107.el7

How reproducible:
Always.

Steps to Reproduce:
LD_PRELOAD=/lib64/libSegFault.so gdb

Actual results:
*** Segmentation fault
Register dump:
...
which backtraced gives:
#0  0x0000000000000000 in ?? ()
#1  0x00000000006a1c94 in internal_vproblem ()
#2  0x00000000006a1ea9 in internal_verror ()
#3  0x00000000006a1f4f in internal_error ()
#4  0x000000000060ea54 in save_original_signals_state ()
#5  0x00000000005dde8f in captured_main ()
#6  0x00000000005dc1ca in catch_errors ()
#7  0x00000000005df2e4 in gdb_main ()
#8  0x00000000004579ae in main ()

Expected results:
(gdb) _

Additional info:

[PATCH] Fix regression: cannot start with LD_PRELOAD=libSegFault.so (PR gdb/18653#c7)
https://sourceware.org/ml/gdb-patches/2017-12/msg00365.html
From: Pedro Alves <palves at redhat dot com>

Reproduced against gdb-7.6.1-107.el7 and verified against gdb-7.6.1-110.el7.

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, 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-2018:0701