All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>
To: shinto.john@smartplayin.com
Cc: ltp-list <ltp-list@lists.sourceforge.net>,
	Naresh Kamboju <naresh.kamboju@linaro.org>,
	ltp-coverage@lists.sourceforge.net
Subject: Re: [LTP] [Ltp-coverage] running LCOV/LTP on Beagle Bone Black - Cannot Allocate Memory Error
Date: Thu, 10 Apr 2014 13:08:31 +0200	[thread overview]
Message-ID: <53467BAF.8030605@linux.vnet.ibm.com> (raw)
In-Reply-To: <1397048671.53348062@apps.rackspace.com>

On 09.04.2014 15:04, shinto.john@smartplayin.com wrote:
> This got resolved when i tried this in KERNEL/mm/Makefile
> 
> GCOV_PROFILE := n
> 
> So basically some issue with KERNEL/mm/vmstat.gcno... right?

If you don't need the coverage data for mm/* then this looks like a
feasible workaround.

> Now i am able to do a complete kernel run.

-- 
Peter Oberparleiter
Linux on System z Development - IBM Germany


------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment 
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

      reply	other threads:[~2014-04-10 11:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-09  4:42 [LTP] [Ltp-coverage] running LCOV/LTP on Beagle Bone Black - Cannot Allocate Memory Error Naresh Kamboju
2014-04-09  9:18 ` shinto.john
2014-04-09 12:31   ` Peter Oberparleiter
2014-04-09 13:04     ` shinto.john
2014-04-10 11:08       ` Peter Oberparleiter [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=53467BAF.8030605@linux.vnet.ibm.com \
    --to=oberpar@linux.vnet.ibm.com \
    --cc=ltp-coverage@lists.sourceforge.net \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=naresh.kamboju@linaro.org \
    --cc=shinto.john@smartplayin.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.