Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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.

Bug 1677918

Summary: Cannot disable "Detaching after fork from child process" message
Product: Red Hat Enterprise Linux 7 Reporter: Tavis Ormandy <taviso>
Component: gdbAssignee: Keith Seitz <keiths>
Status: CLOSED ERRATA QA Contact: Michal Kolar <mkolar>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.7-AltCC: bgollahe, dsmith, gdb-bugs, mcermak, ohudlick, sergiodj, taviso
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gdb-7.6.1-116.el7 Doc Type: No Doc Update
Doc Text:
If this bug requires documentation, please select an appropriate Doc Type value.
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-31 19:09:11 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:
Bug Depends On:    
Bug Blocks: 1710255    

Description Tavis Ormandy 2019-02-16 20:39:37 UTC
Description of problem:

The patch added in bug 235197 means that gdb will always print "Detaching after fork from child process", and there is no way to disable that message. That makes it basically impossible to debug programs that spawn a lot of processes  (e.g. build tools, testcase minimizers, etc), because the console is just spammed with messages and you can never read any text being displayed.

Comment 1 Tavis Ormandy 2019-02-16 20:43:47 UTC
Note that in mainline gdb, you can do `set print inferior-events off`

Comment 3 Keith Seitz 2019-02-20 19:45:27 UTC
The problem with gdb-7.6.1-XXX.el7 is that mainline gdb
has more places where the setting for "print inferior-events" is
checked.

Is using DTS an option? For example, devtoolset-8-gdb is based on
gdb 8.2.

Comment 9 Keith Seitz 2019-08-08 20:41:29 UTC
I've backported the "set print inferior-events" patch mentioned above to -116.el7.
This should not require any additional documentation; it's just a bug fix.

Comment 11 Michal Kolar 2019-11-22 12:44:36 UTC
Reproduced against gdb-7.6.1-115.el7 and verified against gdb-7.6.1-117.el7.

Comment 13 errata-xmlrpc 2020-03-31 19:09:11 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, 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-2020:0993