After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 626979 - Bug-Buddy should allow for manual regeneration of stack traces
Bug-Buddy should allow for manual regeneration of stack traces
Status: RESOLVED WONTFIX
Product: bug-buddy
Classification: Deprecated
Component: general
unspecified
Other All
: Normal enhancement
: ---
Assigned To: Bug-buddy Maintainers
Bug-buddy Maintainers
gnome[unmaintained]
Depends on:
Blocks: 331004
 
 
Reported: 2010-08-15 18:06 UTC by simon80
Modified: 2018-07-16 08:25 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description simon80 2010-08-15 18:06:00 UTC 
This is a sub-task of 331004. KDE's bug reporter has this feature.

When a stack trace is inadequate, the user can go and install debug symbols for the same binary that crashed, if their distribution provides it, but they can't regenerate the backtrace. Bug-buddy should offer a button to force regeneration of the trace.
Comment 1 André Klapper 2018-07-16 08:25:22 UTC 
bug-buddy is not under active development anymore and had its last code changes
many years ago. Its codebase has been archived:
https://gitlab.gnome.org/Archive/bug-buddy/commits/master

Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect
reality (see bug 796784). Please feel free to reopen this ticket (or rather transfer the project to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the responsibility for active development again.