lkml.org 
[lkml]   [2006]   [Jul]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH 00/10] Kernel memory leak detector 0.8
    On 11/07/06, Michal Piotrowski <michal.k.k.piotrowski@gmail.com> wrote:
    > On 11/07/06, Michal Piotrowski <michal.k.k.piotrowski@gmail.com> 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
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2006-07-11 15:03    [W:0.022 / U:0.700 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site