This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/16277] New: gdb virtual memory exhausted
- From: "sami4coding at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Sat, 30 Nov 2013 08:20:01 +0000
- Subject: [Bug gdb/16277] New: gdb virtual memory exhausted
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=16277
Bug ID: 16277
Summary: gdb virtual memory exhausted
Product: gdb
Version: 7.5
Status: NEW
Severity: critical
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: sami4coding at gmail dot com
I tried debugging coredump file using cross toolchain gdb but when i am trying
to execute commands
like:
1. info functions
2. p <some pointer or variable>
gdb is crashing with error message virtual memory exhausted: can't allocate
**** bytes.
**** are some figures and they varies.
Regarding this i have checked available memory on my 64-bit AMD machine and it
is showing around 20GB free memory. Despite of this much memory GDB is failing
for virtual memory exhaustion.
I explored internet and it is only telling changing ulimit will work. I have
modified the virtual limit to unlimited using ulimit but nothing worked. The
same cross gdb is working on different ubuntu machine but failing at my end.
Is this related to gdb source code issue or some settings/configurations are
missing?
( Mine is 2.6.18-128.el5 ( AMD x86-64 ) machine )
ulimit -a showed
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 399360
max locked memory (kbytes, -l) 32
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 399360
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
--
You are receiving this mail because:
You are on the CC list for the bug.