Bug 1375553

Summary:	Regression: gdb --pid $(pidof qemu-system-x86_64) stopped working with gdb 7.11.1
Product:	Red Hat Developer Toolset	Reporter:	Christophe Fergeau <cfergeau>
Component:	gdb	Assignee:	Jan Kratochvil <jan.kratochvil>
Status:	CLOSED ERRATA	QA Contact:	Martin Cermak <mcermak>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	DTS 6.0 RHEL 6	CC:	gbenson, jan.kratochvil, marcandre.lureau, mcermak, mnewsome, ohudlick, palves, pmuldoon, sergiodj, tom
Target Milestone:	beta2	Keywords:	Regression
Target Release:	6.0
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	devtoolset-6-gdb-7.12-0.18.20160928.el7	Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-15 10:12:23 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:

Description Christophe Fergeau 2016-09-13 12:01:43 UTC

run qemu-system-x86_64 (for this reproducer, no need for any arg)
run gdb --pid $(pidof qemu-system-x86_64)
This results in
Attaching to process 27948
[New LWP 27952]
[New LWP 27953]
Warning:
Cannot insert breakpoint -1.
Cannot access memory at address 0x20bf00

(gdb) 0x00007fdf94bcd4b1 in ?? ()

and the gdb session is non-functional.

This started happening with gdb-7.11.1-75.fc24 which is the first gdb 7.11.1 build, downgrading to gdb-7.11-74.fc24 avoids this issue.

Comment 1 Jan Kratochvil 2016-09-14 21:49:38 UTC

136613ef0c6850427317e57be1b644080ff6decb is the first bad commit
Author: Pedro Alves <palves>
    Fix PR gdb/19828: gdb -p <process from a container>: internal error

Comment 4 Jan Kratochvil 2016-09-27 22:24:35 UTC

[patch+7.12] PR gdb/20609 - attach of JIT-debug-enabled inf 7.11.1 regression
https://sourceware.org/ml/gdb-patches/2016-09/msg00387.html

QA: New testfile: gdb.base/jit-attach-pie.exp

Comment 6 Fedora Update System 2016-09-29 15:21:28 UTC

gdb-7.12-0.19.20160929.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-cc57295873

Comment 7 Fedora Update System 2016-09-30 00:23:29 UTC

gdb-7.11.1-86.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-eb3ca41e5d

Comment 8 Fedora Update System 2016-10-03 03:50:12 UTC

gdb-7.11.1-86.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2016-10-09 02:47:20 UTC

gdb-7.12-0.19.20160929.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.

Comment 13 errata-xmlrpc 2016-11-15 10:12:23 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-2016-2737.html