lkml.org 
[lkml]   [2006]   [Jun]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] ignore smp_locks section warnings from init/exit code
On Sun, Jun 11, 2006 at 05:17:40PM -0700, Randy.Dunlap wrote:
> > gdb tells me:
> > (gdb) x/4xa 0x6027b748
> > 0x6027b748 <stdout@@GLIBC_2.2.5>: 0x0 0x0
> > 0x6027b758 <completed.6111+8>: 0x0 0x0
> >
> > So, with stdout@@GLIBC_2.2.5 at 0x6027b748 and completed.6111 at
> > 0x6027b750 - right next to each other - there would seem to be nothing
> > between them to reference anything.
>
> gdb says 0x6027b758 for <completed.6111>, not 0x6027b750 as you
> wrote, so there's 8 more bytes for gunk there. ;)
> Anyway, since I can't build UML, I'm willing to look at the

gdb says 0x6027b758 for <completed.6111+8>, making
completed.6111 = 0x6027b750, leaving 0 bytes for gunk.

Jeff
-
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-06-12 04:32    [W:0.041 / U:0.316 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site