On Mon, Dec 15, 2008 at 11:21:18PM -0500, Benjamin M. Schwartz wrote:
> I'm no expert, but making the system work well without overcommit would
> probably require extensive modifications to the python interpreter, the
> fd.o libraries (dbus, gstreamer, telepathy, etc.), gecko, and maybe even
> X.  All of these would need to allocate only as much memory as they need,
> and react appropriately when malloc returns NULL.  In other words, 'tain't
> gonna happen.

Couldn't we instrument malloc to report when it returns NULL (into an
area of memory we have helpfully set aside for the purpose) and then
report those events during testing, in order to find out and fix those
instances of overallocation?

James Cameron    mailto:qu...@us.netrek.org     http://quozl.netrek.org/
Devel mailing list

Reply via email to