Bug 696220

Summary:	Abrt bugzilla plugin should require gdb
Product:	Red Hat Enterprise Linux 6	Reporter:	David Kutálek <dkutalek>
Component:	abrt	Assignee:	Jiri Moskovcak <jmoskovc>
Status:	CLOSED NOTABUG	QA Contact:	BaseOS QE - Apps <qe-baseos-apps>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.1	CC:	ahecox, dfediuck, dvlasenk, gavin, kklic, npajkovs
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-04-18 12:19:40 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 David Kutálek 2011-04-13 15:25:32 UTC

Description of problem:

Since reporting to bugzilla without backtrace is unwanted and gdb is needed for local backtrace generation, abrt-plugin-bugzilla should require gdb.

Version-Release number of selected component (if applicable):

abrt-plugin-bugzilla-1.1.16-3.el6

How reproducible:

Always

Steps to Reproduce:
1. do a minimal install, without gdb, with abrt bugzilla plugin
2. sleep 10 &; kill -SIGKILL $!
3. abrt-cli -r
  
Actual results:

No backtrace generated, no warning issued.

Expected results:

Installation of abrt-plugin-bugzilla should pull in gdb & eg. abrt-cli should be able to generate backtrace using it.

Additional info:

Comment 1 Jiri Moskovcak 2011-04-18 12:19:40 UTC

There are many reasons why it shouldn't require gdb:

1. gdb is needed only for C/C++ crashes so it should be required by abrt-addon-ccpp - which is the case in Fedora

2. Python exceptions have usable backtrace without gdb (which is actually the same as 1)

3. On RHEL6 we don't generate backtrace on client machine, so that's why gdb is not required and even debuginfo downloading is disabled in config file.