Bug#255495: acknowledged by developer (Re: Bug#255495: gcc-snapshot: Keep debugging symbols)
In my case, I don't really want to debug gcc, but I want to make an
upstream bug report as precise as possible. So including a stack
trace would be a bonus. It should help narrowing the nature of the
bug, so that the appriopriate upstream author can start
investigating, thus saving them time.
Unless it's a trivial problem a stack trace is pretty much always
useless. A good test case is much more important to reproduce and to
properly analyze the problem.
Right. I usually manage to send a short testcase, so all is well. Still,
if stack traces could be present with little penalty in package size, it
would be a bonus. It can also sometimes give a clue when trying to
minimize the testcase.
But I don't insist on the feature, just let it down if it's too much
trouble or inconvenient.
Daniel
Reply to: