Bug 781571

Summary:	Fix Fedora --enablerepo='*-debuginfo' suggestion for RHEL
Product:	Red Hat Enterprise Linux 6	Reporter:	Jan Kratochvil <jan.kratochvil>
Component:	gdb	Assignee:	Jan Kratochvil <jan.kratochvil>
Status:	CLOSED ERRATA	QA Contact:	qe-baseos-tools-bugs
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.2	CC:	jan.kratochvil, mpolacek, pmuller, sergiodj
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	gdb-7.2-52.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-06-20 14:29:44 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Jan Kratochvil 2012-01-13 18:50:17 UTC

Description of problem:
In some cases GDB suggests a command with --enablerepo='*-debuginfo' but what I have heard about RHN Debuginfo channels they are called "rhel-6-server-debug-rpms". This cannot work.

Version-Release number of selected component (if applicable):
gdb-7.2-50.el6.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. ulimit -c unlimited; sleep 1h&
2. kill -SEGV 1649
3. gdb -c ./core.1649

Actual results:
Missing separate debuginfo for the main executable file
Try: yum --disablerepo='*' --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/47/830504b69d8312361b1ed465ba86c9e815b800

Expected results:
Missing separate debuginfo for the main executable file
Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/47/830504b69d8312361b1ed465ba86c9e815b800

Additional info:
Unfortunately QA Beaker machines have completely different setup and I have no access to some real RHN Debug Channel and how it looks like.

Anyway '*-debug*' is backward compatible with '*-debuginfo'.

QA: I do not plan any special testcase for it.

Comment 4 errata-xmlrpc 2012-06-20 14:29:44 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.

http://rhn.redhat.com/errata/RHBA-2012-0930.html