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 306465 - bug buddy doesn't limit backtrace depth
bug buddy doesn't limit backtrace depth
Status: RESOLVED FIXED
Product: bug-buddy
Classification: Deprecated
Component: general
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: Ruben Vermeersch
Bug-buddy Maintainers
: 391112 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-06-04 12:08 UTC by Gabriel de Perthuis
Modified: 2006-12-31 13:32 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement

Attachments
Trivial patch (848 bytes, patch)
2006-12-01 19:44 UTC, Ruben Vermeersch 		none Details | Review

Description Gabriel de Perthuis 2005-06-04 12:08:28 UTC 
It can stall cpu and generate a useless backtrace in the 10000s if need be
(happened with an ephy bug on amd64).
To prevent this, add a «set backtracelimit 200» to gdb-cmd (in /usr/share).
Comment 1 Rhys Moyne 2005-07-21 13:15:01 UTC 
Changing severity to enhancement and marking as new.
Comment 2 Ruben Vermeersch 2006-12-01 19:44:52 UTC 
Created attachment 77507 [details] [review]
Trivial patch

Here's a simple patch. Is this sufficient? If so, should I commit it or will you guys do it?
Comment 3 Fernando Herrera 2006-12-02 14:57:08 UTC 
thanks a lot. Committed to HEAD:

2006-12-01  Ruben Vermeersch  <ruben@savanne.be>

        * src/gdb-cmd: Added "set backtracelimit 200", fixes bug #306465.
Comment 4 Fernando Herrera 2006-12-31 13:32:10 UTC 
*** Bug 391112 has been marked as a duplicate of this bug. ***