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 1348209 - abrt-cli fails to report: backtrace is unusable
Summary: abrt-cli fails to report: backtrace is unusable
Keywords:
Status: CLOSED DUPLICATE of bug 1325795
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: abrt
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: abrt
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-20 12:53 UTC by Michael Petlan
Modified: 2016-06-24 13:26 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-24 13:26:43 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Michael Petlan 2016-06-20 12:53:18 UTC 
Description of problem:

When reporting an issue with abrt-cli, it first tries to install all the necessary debuginfo, but then it fails reporting, saying:

Backtrace is generated and saved, 92168 bytes
Backtrace parsing failed for .
24:0: Frame header variant not recognized.
Loading settings from '/etc/libreport/plugins/bugzilla.conf'
create private bz ticket: 'NO'
groups: '(nil)'
Initializing XML-RPC library
Looking for similar problems in bugzilla
Reporting disabled because the backtrace is unusable.
Please try to install debuginfo manually using the command: "debuginfo-install virt-manager-1.2.1-8.el7" and try again.

When I run the debuginfo-install command, it finds out that everything is already installed. However, ABRT is still failing on it. This happened to me several times, with *different* issues being reported.

I manually looked at tha backtrace file in the abrt issue dir and it looked sane.

Version-Release number of selected component (if applicable):
abrt-addon-xorg-2.1.11-35.el7.x86_64
abrt-gui-libs-2.1.11-35.el7.x86_64
abrt-python-2.1.11-35.el7.x86_64
abrt-addon-kerneloops-2.1.11-35.el7.x86_64
abrt-console-notification-2.1.11-35.el7.x86_64
abrt-dbus-2.1.11-35.el7.x86_64
abrt-gui-2.1.11-35.el7.x86_64
abrt-addon-pstoreoops-2.1.11-35.el7.x86_64
abrt-cli-2.1.11-35.el7.x86_64
abrt-libs-2.1.11-35.el7.x86_64
abrt-addon-vmcore-2.1.11-35.el7.x86_64
abrt-tui-2.1.11-35.el7.x86_64
abrt-desktop-2.1.11-35.el7.x86_64
abrt-addon-ccpp-2.1.11-35.el7.x86_64
gnome-abrt-0.3.4-6.el7.x86_64
abrt-2.1.11-35.el7.x86_64
abrt-addon-python-2.1.11-35.el7.x86_64
rubygem-abrt-0.0.6-2.el7.noarch


How reproducible:
100% on my machine (a RHEL-7.2 box, up-to-date)

Steps to Reproduce:
1. try to report a problem to bugzilla
2.
3.

Actual results:

Reporting proces is aborted due to backtrace problems.

Expected results:

The problem is reported.

Additional info:
Comment 2 Jakub Filak 2016-06-21 06:36:15 UTC 
Thank you for the report. I have a couple of questions:
1. Were all debuginfo packages installed? (This information was above the log lines you have pasted).
2. What version of gdb do you have installed?
3. Is glib2-devel package installed on your machine?
Comment 3 Michael Petlan 2016-06-21 17:31:49 UTC 
1. Before the first abrt-cli reporting attempt not all the debuginfo were installed, so abrt-cli ran the debuginfo-install command which installed them. However, since the backtrace did not seem to be nice enough for abrt-cli, it complained and asked me for running the debuginfo-install command manually. When I did so, yum claimed everything was already installed. Despite that, all other abrt-cli attempts failed in the same way.

I think abrt-cli just did not like the backtrace very much. However, it looked usable in my opinion. Should I share the issue dir to you somehow?

2. gdb-7.6.1-80.el7.x86_64

3. glib2-devel-2.42.2-5.el7.x86_64
Comment 4 Jakub Filak 2016-06-22 08:46:41 UTC 
Michael, can you please uninstall glib2-devel or better upgrade gdb to 7.6.1-88.el7 and re-run the abrt-cli report?

I think this bug report is a duplicate of bug #1325795.
Comment 5 Michael Petlan 2016-06-24 13:26:43 UTC 
Hi, I have devtoolset-4 installed, so I ran the abrt-cli report under DTS this time. DTS has gdb in version 7.11-67.el7. It helped. Thanks. So we may close this bug, since it seems it is realy a gdb bug.

*** This bug has been marked as a duplicate of bug 1325795 ***
Note You need to log in before you can comment on or make changes to this bug.