On 11/07/06, Catalin Marinas <[email protected]> wrote:
On 11/07/06, Michal Piotrowski <[email protected]> wrote:
> On 11/07/06, Michal Piotrowski <[email protected]> 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?
It is kmemleak bug. I wrote "I was wrog" concerning "everything works fine" :)
> 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.
Yes of course. I forgot about this.
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
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/wiki/)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
