This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/20373] New: dump mem <file> 0x400400 -1: Virtual Memory Exhausted (utils.c:1072)
- From: "pieterkockx at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Fri, 15 Jul 2016 04:48:15 +0000
- Subject: [Bug gdb/20373] New: dump mem <file> 0x400400 -1: Virtual Memory Exhausted (utils.c:1072)
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=20373
Bug ID: 20373
Summary: dump mem <file> 0x400400 -1: Virtual Memory Exhausted
(utils.c:1072)
Product: gdb
Version: 7.11.1
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: pieterkockx at gmail dot com
Target Milestone: ---
Arch Linux 4.6.3-1-ARCH
gdb 7.11.1-1
Should be easy to reproduce:
(gdb) r a.out
(gdb) b function
(gdb) dump memory /tmp/dump 0x400400 -1
My intention was to dump "everything in memory", hence the -1 upper-bound.
If this behavior is intentional punishment of clueless programmers, then what
is the canonical command to let gdb "dump everything in memory it has access
to"?
--
You are receiving this mail because:
You are on the CC list for the bug.