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 1149207

Summary:	`catch syscall' doesn't work for parent after `fork' is called
Product:	Red Hat Enterprise Linux 7	Reporter:	Paulo Andrade <pandrade>
Component:	gdb	Assignee:	Sergio Durigan Junior <sergiodj>
Status:	CLOSED ERRATA	QA Contact:	Miroslav Franc <mfranc>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	gdb-bugs, jan.kratochvil, mcermak, mfranc, ohudlick
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	gdb-7.6.1-67.el7	Doc Type:	Bug Fix
Doc Text:	The "catch syscall" command uses a special type of breakpoint inside GDB, which is not maintained by the regular code that handles normal breakpoints. Previously, GDB was incorrectly removing these system call catchpoints when the program being debugged forked itself, which made GDB miss any subsequent system call that needed to be caught. As a consequence, GDB was not able to properly catch a system call in the parent process after a call to "fork". With this update, GDB no longer removes a system call catchpoint from a program that forked itself. As a result, GDB is now able to correctly stop at a system call that is called from the parent process after it has forked.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-19 13:02:46 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:	1149205
Bug Blocks:

Description Paulo Andrade 2014-10-03 14:02:55 UTC

Alias to #1149205 to also report for rhel-7.

https://sourceware.org/bugzilla/show_bug.cgi?id=13457

This problem does not happen in fedora 20:

$ rpm -q gdb
gdb-7.7.1-18.fc20.x86_64

but happens in rhel-6.4 (after updates):

$ rpm -q gdb
gdb-7.2-64.el6_5.2.x86_64

and also happens in rhel-7:

$ rpm -q gdb
gdb-7.6.1-51-el7.x86_64

Comment 7 errata-xmlrpc 2015-11-19 13:02:46 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://rhn.redhat.com/errata/RHBA-2015-2089.html