[Bug gdb/17963] New: Handle running out of memory better

["dje at google dot com" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=17963

            Bug ID: 17963
           Summary: Handle running out of memory better
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: dje at google dot com

There are cases where gdb just needs a lot of memory.
e.g., long debugging sessions of monster programs.
I have some benchmarks that don't complete with 32GB memory + 32GB swap because
they OOM.

Also, gdb is sometimes used on memory constrained machines, and running out of
memory is just not friendly.

Thus, gdb should manage its memory better.

1) User should be able to say "don't use more than X" (or at least "try not to
use more than X").

2) If gdb OOMs it should try to free up some memory and try again.
E.g., it could throw out some debug info and read it in again as necessary.

-- 
You are receiving this mail because:
You are on the CC list for the bug.