From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: Justin Mattock <justinmattock@gmail.com>
Cc: Dave Korn <dave.korn.cygwin@googlemail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
gcc@gcc.gnu.org, KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
David Rientjes <rientjes@cs.washington.edu>
Subject: Re: cc1plus invoked oom-killer: gfp_mask=0x280da, order=0, oom_adj=0
Date: Thu, 05 Nov 2009 00:36:28 +0000 [thread overview]
Message-ID: <4AF21E0C.90506@gmail.com> (raw)
In-Reply-To: <dd18b0c30911041322y2cfd58f8m168550bbe3e8234b@mail.gmail.com>
Justin Mattock wrote:
> here's what I did:
> valgrind --tool=memcheck --leak-check=full -v make -f client.mk build
> ==4072== LEAK SUMMARY:
> I'll try out gdb, and more of valgrind.
Yep, that doesn't tell us a lot in its default modes. I'm not a valgrind
expert but it looks from the docs like you want to try the Massif tool: it
looks really thorough.
http://valgrind.org/docs/manual/ms-manual.html
cheers,
DaveK
next prev parent reply other threads:[~2009-11-05 0:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 21:29 cc1plus invoked oom-killer: gfp_mask=0x280da, order=0, oom_adj=0 Justin Mattock
2009-11-02 21:49 ` Jiri Slaby
2009-11-02 22:02 ` Justin Mattock
2009-11-02 22:05 ` Jiri Slaby
2009-11-02 22:12 ` Justin P. Mattock
2009-11-03 0:56 ` Justin P. Mattock
2009-11-04 1:18 ` KOSAKI Motohiro
2009-11-04 1:40 ` Justin P. Mattock
2009-11-04 6:24 ` Andrew Morton
2009-11-04 6:44 ` Justin P. Mattock
2009-11-04 9:14 ` Jiri Slaby
2009-11-04 9:32 ` KOSAKI Motohiro
2009-11-04 15:28 ` Andrew Morton
2009-11-04 23:20 ` KOSAKI Motohiro
2009-11-04 13:13 ` Dave Korn
2009-11-04 15:08 ` Justin P. Mattock
2009-11-04 15:45 ` Dave Korn
2009-11-04 16:39 ` Justin Mattock
2009-11-04 19:48 ` Dave Korn
2009-11-04 20:39 ` Justin P. Mattock
2009-11-04 21:22 ` Justin Mattock
2009-11-05 0:36 ` Dave Korn [this message]
2009-11-05 3:36 ` Justin Mattock
2009-11-05 5:08 ` Dave Korn
2009-11-06 21:21 ` Justin P. Mattock
2009-11-10 2:55 ` Justin P. Mattock
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=4AF21E0C.90506@gmail.com \
--to=dave.korn.cygwin@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=gcc@gcc.gnu.org \
--cc=justinmattock@gmail.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@cs.washington.edu \
/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