Advertisement
Managed Dedicated Servers - HC Servers
Dedicated and managed servers in U.S and Europe. Famous 24x7 support and customizations from HCServers.net!
Sponsored link
Serve your customers, not your servers, with VERIO Linux VPS. Full-access test-drive here.
| Weekly edition | Kernel | Security | Distributions | Search |
| Archives | Calendar | Subscribe | Write for LWN | LWN.net FAQ |
Buggifying critical core modules
Buggifying critical core modules
Posted Mar 19, 2008 15:43 UTC (Wed) by paulj (subscriber, #341)In reply to: Buggifying critical core modules by ncm
Parent article: Who maintains dpkg?
Changing (e.g.) "(char*)0" to NULL introduces a gratuitous bug into correct code.
On any platforms that matter though?
(Log in to post comments)
Buggifying critical core modules
Posted Mar 19, 2008 19:52 UTC (Wed) by ncm (subscriber, #165) [Link]
What does "that matter" mean? Usually it seems to mean "that I have". We've learned painfully, again and again, that choosing that definition leads to pain. It's easy to follow the correct rule: "in a varargs call, always pass the correct type." Doing what you know is incorrect just because it happens to work on your own hardware is little different from sabotage.
Buggifying critical core modules
Posted Mar 22, 2008 10:19 UTC (Sat) by sandmann (subscriber, #473) [Link]
Fine, let's define "matter" as "exist". Which platforms are we worrying about?
Buggifying critical core modules
Posted Mar 20, 2008 16:16 UTC (Thu) by liljencrantz (subscriber, #28458) [Link]
All 64-bit x86 CPUs. That's only the second most common platform to run Linux on.