This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFC] What to do on VM exhaustion
- From: Michael Snyder <michsnyd at cisco dot com>
- To: kmacy at fsmware dot com
- Cc: Paul Koning <pkoning at equallogic dot com>, gdb at sources dot redhat dot com, gdb-patches at sources dot redhat dot com, wendyp at cisco dot com
- Date: Thu, 05 Jan 2006 17:35:18 -0800
- Subject: Re: [RFC] What to do on VM exhaustion
- References: <43BC6F36.3050000@cisco.com> <17341.12827.191000.952900@gargle.gargle.HOWL> <43BD9703.6080403@cisco.com> <b1fa29170601051725t2fc37a96r2dc959a45a2aa92f@mail.gmail.com>
Kip Macy wrote:
Why not just pre-allocate a small arena at startup for an "emergency"
malloc? Hardly ideal, but it would allow gdb to fail gracefully.
Wouldn't that require modifying malloc?
Or do you have in mind that, on detecting out-of-VM, we would
free our little reserved chunk, thus making it available for
libc (or whatever)?
Hmmm, I suppose that might work...