On Sat, Oct 05, 2013 at 07:15:33PM -0700, Octavio Alvarez wrote:
Reporting the bug has turned pointless now; you know what happens: incomplete debugging information makes it more difficult for upstream. That's why if I report a bug without a full backtrace, chances of the bug being disregarded as NEEDINFO raise significantly. And upstream will just blame the reporter.
Please, show examples of this for coreutils. I've been working with this code for something like 15 years, and off the top of my head I can't remember a case where lack of a backtrace kept something from getting fixed. strace is usually the most useful debugging output, because most of the problems end up being with the kernel or libc doing something unexpected. The coreutils code just isn't so complicated that it's hard to figure out where something is going wrong (most of the utilities are relatively thin wrappers around system calls). For something like a web browser, yeah, the backtrace might be helpful. But you're asking for a debug version of this package, and you haven't yet shown why it is useful FOR THIS PACKAGE. Just saying over and over again that it's needed for upstream isn't helpful, as it simply isn't true (in my experience) for this code.
Mike Stone -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
