linux-kernel - Re: cc1plus invoked oom-killer: gfp_mask=0x280da, order=0, oom

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4AF1E66D.6060705@gmail.com>
Date:	Wed, 04 Nov 2009 12:39:09 -0800
From:	"Justin P. Mattock" <justinmattock@...il.com>
To:	Dave Korn <dave.korn.cygwin@...glemail.com>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	gcc@....gnu.org, KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	David Rientjes <rientjes@...washington.edu>
Subject: Re: cc1plus invoked oom-killer: gfp_mask=0x280da, order=0, oom_adj=0

Dave Korn wrote:
> Justin Mattock wrote:
>
>    
>> O.k. here is the info from dmesg(with the patch added)
>> and what -fmem-report:
>>      
>
>    I don't know how to read the oom dmesg, but as to the -fmem-report:
>
>    
>> Memory still allocated at the end of the compilation process
>> Size   Allocated        Used    Overhead
>> Total       7200k       5293k        104k
>>      
>
> ... what that's telling us is that there isn't a substantial leak in GCC, as
> there's only 7 meg left unreclaimed by GC at the end.  I think we'll have to
> wait and see what the debugger tells us; either GCC really is using that much
> memory in processing the file, or there's some kind of system or kernel bug
> you're running into that is causing a leak in the VMM rather than the application.
>
>    
just finished compiling and installing gdb/valgrind
>> String pool
>>      
>
>    
>> bytes           86k (17592186044415M overhead)
>>      
>
>    0xFFFFFFFFFFF00000, lol, wut?  It's possible that indicates some sort of
> memory corruption going on.  Maybe valgrind can help, do you have that?
>
>      cheers,
>        DaveK
>
>
>    
Not sure how to use these.(need to read)
Any quick commands I can do to get the info
to you?

Justin P. Mattock
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/