News for hackers. Stuff that matters.
Re:Something is deeply broken in OS X memory management by munin on Monday April 23, 2012 @12:13PM (#3879509)
the OS X kernel is open source. so why aren't people reading it to figure out where this bug is?
Re:Something is deeply broken in OS X memory management by kevingadd on Monday April 23, 2012 @12:25PM (#3879587)
Yeah, I'm sure if you just read the Darwin kernel there's a '#define USE_LOTS_OF_MEMORY 1' in there that you can change.

The class of problems described in the original post are not the sort of thing you 'just find' by glancing at kernel source code. The problems described sound like they could be an issue of poorly tuned heuristics/thresholds, or necessitate some extra machinery inside the OS X memory manager that isn't there currently. It's not like you can send Apple a pull request on github.

Re:Something is deeply broken in OS X memory management by jfb on Monday April 23, 2012 @12:29PM (#3879609)
But given enough eyes all bugs are shallow! Are you implying that ESR is full of shit?
Re:Something is deeply broken in OS X memory management by munin on Monday April 23, 2012 @12:27PM (#3879598)
yes I know, that's the point of my question ;)

everyone is all positive about "open source" until they have to dive into a few millions lines of complicated system-level C code and then...

Re:Something is deeply broken in OS X memory management by RickHull on Monday April 23, 2012 @02:26PM (#3880220)
> yes I know, that's the point of my question ;)

It's a facile point.

> everyone is all positive about "open source" until they have to dive into a few millions lines of complicated system-level C code and then...

Does anyone doubt that 99% of open source users never read a line of the source code which they are using? The point is, they have the opportunity to, and more importantly, the 1% (or whatever) with the skills and resources are able to actually do something about it.

If you don't have the ability to change or examine the source code, then there is little incentive to do any runtime analysis which might illuminate the problem.

Re:Something is deeply broken in OS X memory management by wickedchicken on Monday April 23, 2012 @01:23PM (#3879907)
> and then...

become immensely employable.

Re:Something is deeply broken in OS X memory management by xpaulbettsx on Monday April 23, 2012 @02:56PM (#3880366)
What are you gonna do about it when you find and fix the bug? You can't run a custom kernel on OS X.
Re:Something is deeply broken in OS X memory management by daniel02216 on Monday April 23, 2012 @11:00PM (#3882221)
Re:Something is deeply broken in OS X memory management by xpaulbettsx on Tuesday April 24, 2012 @01:56AM (#3882641)
None of these posts detail how to actually replace the kernel, only how to build it, nor what happens when Apple ships an update that changes the kernel.
Re:Something is deeply broken in OS X memory management by comex on Tuesday April 24, 2012 @12:20PM (#3884653)
You install the kernel by running make install, then copying the stuff in BUILD/dst to /. (If you haven't changed any APIs accessible to kexts, you can get away with just copying mach_kernel.) When Apple ships an update, you compile the new kernel.
Re:Something is deeply broken in OS X memory management by taligent on Monday April 23, 2012 @04:57PM (#3880929)
Do what normal people do. Tell Apple:

http://bugreporter.apple.com