Calling for a new openSUSE development model

Posted Jun 18, 2012 3:51 UTC (Mon) by k8to (guest, #15413)
In reply to: Calling for a new openSUSE development model by jengelh
Parent article: Calling for a new openSUSE development model

Your level of hostility is off the charts.

Suse 10.1 through 10.4 specifically bound the resolver library tightly by modifying the symbol table with the system allocator to work around firefox bugs. This meant that any executable using an alternate allocator on these versions would end up trying to free memory with the custom allocator which wasn't allocated with it. A crash at this point was about the best outcome you could hope for.

The bug is documented and filed.

There are others I remember less well.

Take your baseless presumptions and go home.

Calling for a new openSUSE development model

Posted Jun 18, 2012 9:42 UTC (Mon) by jengelh (subscriber, #33263) [Link] (3 responses)

>Suse 10.1 through 10.4

My point is that blaming something today for issues it has had in the past is unjustified. (Just like certain political developments in the real world.)

Calling for a new openSUSE development model

Posted Jun 18, 2012 9:52 UTC (Mon) by k8to (guest, #15413) [Link] (1 responses)

I'm not done debugging the current problem that only shows up on SLES and no other linux distribution that is resulting in memory corruption completely at random.

Calling for a new openSUSE development model

Posted Jun 18, 2012 9:53 UTC (Mon) by k8to (guest, #15413) [Link]

Meanwhile, we do have customers who run those versions, so it's not exactly the past.

Calling for a new openSUSE development model

Posted Jun 18, 2012 15:55 UTC (Mon) by nevyn (guest, #33129) [Link]

> My point is that blaming something today for issues it has had in
> the past is unjustified.

So much sarcasm ... so little time. I shall save my energy and just highlight your words.

Calling for a new openSUSE development model

Posted Jul 8, 2012 1:21 UTC (Sun) by cmccabe (guest, #60281) [Link]

I actually like using SuSE on my personal desktop, so I'm sad to hear about these 10.x problems. Do you have a bug number? My Google skills are weak today, apparently. The number of people using SuSE may be small, but it's not zero (for us), and I hope I don't end up having to debug something like this in the future.