Bug 1852580

Summary:	GDB backgrounds self when it errors
Product:	Red Hat Enterprise Linux 8	Reporter:	Keith Seitz <keiths>
Component:	gdb	Assignee:	Keith Seitz <keiths>
gdb sub component:	system-version	QA Contact:	Michal Kolar <mkolar>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	unspecified	CC:	bcrocker, dsmith, gdb-bugs, keiths, mcermak, ohudlick, qe-baseos-tools-bugs, sergiodj
Version:	8.4	Keywords:	Bugfix, Triaged
Target Milestone:	rc
Target Release:	8.0
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	gdb-8.2-13.el8	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:	1850710	Environment:
Last Closed:	2021-05-18 15:46:02 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:	1894575

Description Keith Seitz 2020-06-30 18:12:49 UTC

+++ This bug was initially created as a clone of Bug #1850710 +++

Description of problem:

When I attempt to single-step into JIT-compiled code on S390x,
my gdb process gets stopped and backgrounded as soon as I execute
the basr instruction that called the JIT-compiled function.
I can fg the process, at which point gdb reports "PC not saved."
If I stepi again, exactly the same thing happens.

Each time I fg the process, I can see the pc incrementing, and
instruction effects (e.g. changes to contents of general registers)
have clearly taken place.  The command "disp/i $pc" works as
expected.  The "disassemble" command works fine, e.g.
disassemble $pc, $pc+10.

*** This bug tracks the terminal issues reported in the original bug. ***

Comment 5 Michal Kolar 2020-11-17 21:00:42 UTC

Reproduced against gdb-8.2-12.el8 and verified against both gdb-8.2-13.el8 and gdb-8.2-14.el8.

Comment 8 Michal Kolar 2020-11-23 15:42:23 UTC

Verified against gdb-8.2-14.el8.

Comment 10 errata-xmlrpc 2021-05-18 15:46:02 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 (gdb bug fix and enhancement update), 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-2021:1836