From: Aarthy <aarthy82@gmail.com>
To: gdb@sourceware.org
Subject: reg: GDB's generate-core-file option
Date: Tue, 29 Sep 2009 02:09:00 -0000 [thread overview]
Message-ID: <30ca7ede0909281909n40cccc62m8e3c574546f7208f@mail.gmail.com> (raw)
Hi there,
I am currently working on a product which has many processes running
in a multi threaded fashion. I run my product on a device which has
200 MB of hard disk space to write the core file. It doesn't have any
swap memory as such. My requirement is that I need to collect the
snapshot of each process at a particular time. So I used
generate-core-file option after attaching each process to GDB. The
problem is that for one process i get the following error.
warning: Failed to write corefile contents (No space left on device).
../../gdb/utils.c:1058: internal-error: virtual memory exhausted:
can't allocate 92123136 bytes.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
I would like to know what could be the reason. I have about 15
processes running. everything except this process i was able to
generate the forced core file.
This is my ulimit -a output,
Linux(debug)# ulimit -a
core file size (blocks, -c) 73242
data seg size (kbytes, -d) 62500
file size (blocks, -f) unlimited
max locked memory (kbytes, -l) unlimited
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
stack size (kbytes, -s) unlimited
cpu time (seconds, -t) unlimited
max user processes (-u) 26624
virtual memory (kbytes, -v) 125000
If i change the virtual memory size to unlimited i was able to
generate the core. Kindly let me know how exactly the
generate-core-file works.
Regards,
Aarthy.
next reply other threads:[~2009-09-29 2:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 2:09 Aarthy [this message]
2009-09-29 3:25 ` Hui Zhu
2009-09-29 4:32 ` Michael Snyder
2009-09-29 10:20 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=30ca7ede0909281909n40cccc62m8e3c574546f7208f@mail.gmail.com \
--to=aarthy82@gmail.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox