Re: Need help with debugging (gcc bug?)

2007-11-27 Thread Mulyadi Santosa
Hi... Coming a bit late.. As you see, with -Os, this produces: /* THIS FIELD IS ONLY 16 BITS */ movl4(%ebx), %eax movw%ax, (%esi) While the no-optimizations code looks like this: movl8(%ebp), %eax movzwl 4(%eax), %eax movl%eax, %

Re: Need help with debugging (gcc bug?)

2007-11-20 Thread Vegard Nossum
On Nov 20, 2007 12:16 PM, Vegard Nossum <[EMAIL PROTECTED]> wrote: > Hello, > > Running kmemcheck, I got the following: > kmemcheck: Caught uninitialized read from EIP = c11aeba6 > (sock_init_data+0xa6/0x17a), address c341a024, size 32 > [] error_code+0x72/0x78 > [] sock_init_data+0xa6/0x17a > [

Re: Need help with debugging (gcc bug?)

2007-11-20 Thread Michael Blizek
Hi! This site may be interesting to you: http://kerneltrap.org/Linux/Compiler_Optimization_Bugs_and_World_Domination Yours, Michi -- programing a layer 3+4 network protocol see http://michaelblizek.homelinux.net -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" t

Re: Need help with debugging (gcc bug?)

2007-11-20 Thread Vegard Nossum
On Nov 20, 2007 12:43 PM, Vegard Nossum <[EMAIL PROTECTED]> wrote: > On Nov 20, 2007 12:16 PM, Vegard Nossum <[EMAIL PROTECTED]> wrote: > > Here, offsetof(struct socket, type) = 0x24, like the one used in the > > reads/writes. The type here is short, on 386 that's 16 bits. So why is > > gcc later r

Need help with debugging (gcc bug?)

2007-11-20 Thread Vegard Nossum
Hello, Running kmemcheck, I got the following: kmemcheck: Caught uninitialized read from EIP = c11aeba6 (sock_init_data+0xa6/0x17a), address c341a024, size 32 [] error_code+0x72/0x78 [] sock_init_data+0xa6/0x17a [] __netlink_create+0x3b/0x85 [] netlink_kernel_create+0x59/0x148 [] xfrm_user_in