Classic bug reports

#1

Post by _wrlv » Thu, Oct 01, 2015, 5:28 AM UTC

Re: Classic bug reports

#2

Post by chris_wot » Thu, Oct 01, 2015, 10:00 AM UTC

Ulrich Drepper strikes again: https://sourceware.org/bugzilla/show_bug.cgi?id=12701

For a smart guy, when he's wrong he is completely wrong. And any good work he might have done is wiped out by his arrogance. Not to mention he prevented bugs from being fixed.

But here is my favourite bug that cannot be fixed:

https://bugzilla.gnome.org/show_bug.cgi?id=650371

Basically, the number of steps on Gnome volume control can't be configurable because apparently there are no situations you would ever want to do that. Except for hardware setups that don't report back volume information...

Re: Classic bug reports

#3

Post by jeremysalwen » Thu, Oct 01, 2015, 10:18 AM UTC

chris_wot wrote: post #2

Ulrich Drepper strikes again: https://sourceware.org/bugzilla/show_bug.cgi?id=12701 For a smart guy, when he's wrong he is completely wrong. And any good work he might have done is wiped out by his arrogance. Not to mention he prevented bugs from being fixed. But here is my favourite bug that cannot be fixed: https://bugzilla.gnome.org/show_bug.cgi?id=650371 Basically, the number of steps on Gnome volume control can'…

The worst part about people who respond to bug reports in that way is that for most people, it just intimidates you into thinking you are wrong, and stupid for even asking. It's like an amature trying to beat a lawyer in court, you can't win, even if you're right.

Re: Classic bug reports

#4

Post by ploxiln » Thu, Oct 01, 2015, 10:43 AM UTC

chris_wot wrote: post #2

Ulrich Drepper strikes again: https://sourceware.org/bugzilla/show_bug.cgi?id=12701 For a smart guy, when he's wrong he is completely wrong. And any good work he might have done is wiped out by his arrogance. Not to mention he prevented bugs from being fixed. But here is my favourite bug that cannot be fixed: https://bugzilla.gnome.org/show_bug.cgi?id=650371 Basically, the number of steps on Gnome volume control can'…

My favorite Drepper bug thread: strfry() gives skewed distributions https://sourceware.org/bugzilla/show_bug.cgi?id=4403

Re: Classic bug reports

#5

Post by nmc » Thu, Oct 01, 2015, 10:57 AM UTC

> Alas, Ubuntu Bug 1 is still unfixed

What? Status is shown as "Fix Released", since the rise of Android and iOS has shrunk Microsoft's market share.

Re: Classic bug reports

#6

Post by dunkelheit » Thu, Oct 01, 2015, 12:04 PM UTC

Although in slightly different vein and, strictly speaking, not reported to a public bug tracker, this AMD CPU bug report by Matt Dillon is probably my favourite (link: https://www.dragonflybsd.org/mailarchive/kernel/2012-03/msg0...). Tracking the intermittent problem to the lowest level and blaming the CPU and not the numerous layers above it surely takes guts.

Re: Classic bug reports

#7

Post by tempodox » Thu, Oct 01, 2015, 12:21 PM UTC

You can say what you want about Drepper, but as far as scanf() and siblings are concerned, there is only one one safe way of using them: Not using them. Better write comprehensible reliable code to implement input scanning.

Re: Classic bug reports

#8

Post by tedunangst » Thu, Oct 01, 2015, 1:18 PM UTC

tempodox wrote: post #7

You can say what you want about Drepper, but as far as scanf() and siblings are concerned, there is only one one safe way of using them: Not using them. Better write comprehensible reliable code to implement input scanning.

But he didn't just say you're better off not using scanf(). He insisted, quite incorrectly, that that the glibc behavior was correct.

Re: Classic bug reports

#9

Post by teh_klev » Thu, Oct 01, 2015, 2:07 PM UTC

jeremysalwen wrote: post #3

chris_wot wrote: post #2

Ulrich Drepper strikes again: https://sourceware.org/bugzilla/show_bug.cgi?id=12701 For a smart guy, when he's wrong he is completely wrong. And any good work he might have done is wiped out by his arrogance. Not to mention he prevented bugs from being fixed. But here is my favourite bug that cannot be fixed: https://bugzilla.gnome.org/show_bug.cgi?id=650371 Basically, the number of steps on Gnome volume control can'…

The worst part about people who respond to bug reports in that way is that for most people, it just intimidates you into thinking you are wrong, and stupid for even asking. It's like an amature trying to beat a lawyer in court, you can't win, even if you're right.

>It's like an amature trying to beat a lawyer in court

I see what you did there:

https://bugzilla.mozilla.org/show_bug.cgi?id=362178

:)

Re: Classic bug reports

#10

Post by 36erhefg » Thu, Oct 01, 2015, 7:23 PM UTC

dunkelheit wrote: post #6

Although in slightly different vein and, strictly speaking, not reported to a public bug tracker, this AMD CPU bug report by Matt Dillon is probably my favourite (link: https://www.dragonflybsd.org/mailarchive/kernel/2012-03/msg0... ). Tracking the intermittent problem to the lowest level and blaming the CPU and not the numerous layers above it surely takes guts.

How do you even fix that? Do you have to update every compiler so it checks the generate machine code for that problematic sequence and insert some nop's, or is there a way to update the cpu itself?