From: corpaul <c.bezemer@tudelft.nl>
To: systemtap@sourceware.org
Subject: 'random' Allocation failed errors
Date: Fri, 30 Aug 2013 10:12:00 -0000 [thread overview]
Message-ID: <1377857543834-242637.post@n7.nabble.com> (raw)
When I run probes, I get allocation errors now and then. They appear to be
fairly random, because I am probing the same task (a unit test suite) so
memory usage should be approximately the same.
example:
ERROR: global variable 'times' allocation failed
Sometimes systemtap gives me a suggestion for which parameter should be
increased (e.g. DMAXMAPENTRIES), sometimes it doesn't. I am running the
probes with the following parameters:
-DMAXMAPENTRIES=120000 -DSTP_NO_OVERLOAD -DMAXSTRINGLEN=4096
-DTRYLOCKDELAY=300 -DMAXSKIPPED=10000 -DMAXACTION=1000
Are these perhaps exceptionally low/high values? How should I deal with
these allocation errors?
Thanks!
--
View this message in context: http://sourceware-org.1504.n7.nabble.com/random-Allocation-failed-errors-tp242637.html
Sent from the Sourceware - systemtap mailing list archive at Nabble.com.
next reply other threads:[~2013-08-30 10:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 10:12 corpaul [this message]
2013-08-30 13:42 ` Frank Ch. Eigler
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=1377857543834-242637.post@n7.nabble.com \
--to=c.bezemer@tudelft.nl \
--cc=systemtap@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).