public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: fche@redhat.com (Frank Ch. Eigler)
To: corpaul <c.bezemer@tudelft.nl>
Cc: systemtap@sourceware.org
Subject: Re: 'random' Allocation failed errors
Date: Fri, 30 Aug 2013 13:42:00 -0000	[thread overview]
Message-ID: <y0mr4dbjogs.fsf@fche.csb> (raw)
In-Reply-To: <1377857543834-242637.post@n7.nabble.com> (c.bezemer@tudelft.nl's message of "Fri, 30 Aug 2013 03:12:23 -0700 (PDT)")


corpaul <c.bezemer@tudelft.nl> writes:

> 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 [...]

dsmith's recent change to the systemtap runtime (PR15805, commit
3f873e53) changes the way that large data structures like the script
hash tables are allocated.  Would you mind trying git systemtap a try?

- FChE

      reply	other threads:[~2013-08-30 13:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-30 10:12 corpaul
2013-08-30 13:42 ` Frank Ch. Eigler [this message]

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=y0mr4dbjogs.fsf@fche.csb \
    --to=fche@redhat.com \
    --cc=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).