Re: [PATCH 00/10] Kernel memory leak detector 0.8

[Joseph Fannin]

On Tue, Jul 11, 2006 at 02:00:05PM +0100, Catalin Marinas wrote:
> On 11/07/06, Michal Piotrowski <michal.k.k.piotrowski@xxxxxxxxx> wrote:
> >On 11/07/06, Michal Piotrowski <michal.k.k.piotrowski@xxxxxxxxx> 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.

    Which gcc versions are affected by this?
--
Joseph Fannin
jhf@xxxxxxxxxxxxxx

"Bull in pure form is rare; there is usually some contamination by data."
    -- William Graves Perry Jr.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/