GNOME Bugzilla – Bug 347556
bug-buddy should be able to get complete stack trace to help developers analysing a bug.
Last modified: 2006-07-15 00:55:12 UTC
bug-buddy some times is not able to get the required stack trace. I see below message in lot of evolution bug updates. <snip> that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. <snip> Some times the user who submits the bug is not able to get back to the developer with the required stack trace for various reasons and the developer cannot fix the bug because the user have not given the required info.
Well, the message you see is a standardized message that can be pasted with the click of a mouse. The thing is, that debugging symbols, which are requested by that message are often stripped out by distributions. Why? Because they waste a lot of precious space, and many users never help debug bugs anyway... Bug buddy gets the best stack trace that is possible, and if the user really does want to help out, he can follow the instructions and help reproduce the bug... Not much that can be done by bug-buddy, I'm afraid...
Bug-Buddy could either: 1. Submit MD5 sums of all libs, and have a server which does the 'add debug symbol magic'. This is very very very hard to do. 2. Automatically install required debug symbols for the user. Also very hard as this differs per distro and not every distro has debug symbols for every package.
*** This bug has been marked as a duplicate of 331004 ***