LWN.net Logo

Glibc change exposing bugs

Glibc change exposing bugs

Posted Nov 10, 2010 20:05 UTC (Wed) by gus3 (guest, #61103)
In reply to: Glibc change exposing bugs by mattdm
Parent article: Glibc change exposing bugs

Or, one that dumps core and/or logs to /var/log/debug (or whatever is configured to handle debugging messages). The more noise it makes, the more likely it is to get fixed, and quickly, once distributors start getting lots of automated backtraces in their bug trackers.

I learned the difference between memcpy() and memmove() in my very first C programming class. Adobe should be embarrassed that their programmers can't read documentation.


(Log in to post comments)

Glibc change exposing bugs

Posted Nov 11, 2010 12:38 UTC (Thu) by nye (guest, #51576) [Link]

Even better would be if we could design a system that *shoots the user in the head* every time a programmer writes something that isn't mathematically proven to be flawless in design and implementation.

That would be open source utopia I think.

Glibc change exposing bugs

Posted Nov 11, 2010 14:46 UTC (Thu) by nix (subscriber, #2304) [Link]

I would support such a system as long as large-calibre weapons were used and the option was available to remotely shoot the developer instead.

;}

Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds