Skip to content

[Bug] Provide a more actionable error message when unable to report a bug due to absent debug symbols. #390

@RokeJulianLockhart

Description

@RokeJulianLockhart

Example

Similar to #386 (comment):

--- Running report_uReport ---
('report_uReport' completed successfully)

--- Running analyze_CCpp ---
Generating backtrace
Backtrace is generated and saved, 19026 bytes
Backtrace parsing failed for .
1:0: No frame and no thread found.

--- Running analyze_BodhiUpdates ---
Looking for similar problems in bugzilla

...I am unable to report a bug in 1.4.3-4.fc42 because I see "no frame and no thread found".

Environment

  1. #!/usr/bin/env sh
    rpm -qa | grep abrt
  2. abrt-libs-2.17.6-4.fc42.x86_64
    abrt-dbus-2.17.6-4.fc42.x86_64
    python3-abrt-2.17.6-4.fc42.x86_64
    abrt-2.17.6-4.fc42.x86_64
    abrt-addon-kerneloops-2.17.6-4.fc42.x86_64
    abrt-addon-ccpp-2.17.6-4.fc42.x86_64
    abrt-addon-pstoreoops-2.17.6-4.fc42.x86_64
    abrt-addon-vmcore-2.17.6-4.fc42.x86_64
    abrt-addon-xorg-2.17.6-4.fc42.x86_64
    abrt-plugin-bodhi-2.17.6-4.fc42.x86_64
    python3-abrt-addon-2.17.6-4.fc42.noarch
    abrt-tui-2.17.6-4.fc42.noarch
    gnome-abrt-1.4.3-4.fc42.x86_64
    abrt-gui-libs-2.17.6-4.fc42.x86_64
    abrt-gui-2.17.6-4.fc42.x86_64
    abrt-desktop-2.17.6-4.fc42.x86_64
    abrt-cli-2.17.6-4.fc42.x86_64

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions