From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750733AbWGKNAH (ORCPT ); Tue, 11 Jul 2006 09:00:07 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751275AbWGKNAH (ORCPT ); Tue, 11 Jul 2006 09:00:07 -0400 Received: from nz-out-0102.google.com ([64.233.162.194]:63658 "EHLO nz-out-0102.google.com") by vger.kernel.org with ESMTP id S1750733AbWGKNAG (ORCPT ); Tue, 11 Jul 2006 09:00:06 -0400 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=jQLl1GnaILboPJSE0Ww2w68s2LJPcSed6dprAgTg9Eald/R5WNERLQGFb9vkolLrX9Qu+34BlbKN+tVAJDGXKwxNjY9vUTLlYPcm+3bC9bJVX0rZfqtO/eVdJG7ClB49lCVOLaKfyMh6HCZ7IXC+nMLBj5gXS1xPrJL14USfI1I= Message-ID: Date: Tue, 11 Jul 2006 14:00:05 +0100 From: "Catalin Marinas" To: "Michal Piotrowski" Subject: Re: [PATCH 00/10] Kernel memory leak detector 0.8 Cc: linux-kernel@vger.kernel.org In-Reply-To: <6bffcb0e0607110551v272deebcua5dc3f782ed25a7f@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20060710220901.5191.66488.stgit@localhost.localdomain> <6bffcb0e0607110527x4520d5bbne8b9b3639a821a18@mail.gmail.com> <6bffcb0e0607110546r11d2f619pbcd1205999253bd@mail.gmail.com> <6bffcb0e0607110551v272deebcua5dc3f782ed25a7f@mail.gmail.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On 11/07/06, Michal Piotrowski wrote: > On 11/07/06, Michal Piotrowski wrote: > > When I set DEBUG_KEEP_INIT=n everything works fine. > > I was wrong. You mean the previous e-mail wasn't a kmemleak bug? > Here is the new error > /usr/src/linux-work4/kernel/pid.c: In function 'pid_task': > /usr/src/linux-work4/kernel/pid.c:262: error: initializer element is > not constant > /usr/src/linux-work4/kernel/pid.c:262: error: (near initialization for > '__memleak_offset__container_of.offset') > make[2]: *** [kernel/pid.o] Error 1 > make[1]: *** [kernel] Error 2 > make: *** [_all] Error 2 That's a bug in gcc-4. The __builtin_constant_p() function always returns true even when the argument is not a constant. You could try a gcc-3.4 or a patched gcc. -- Catalin