Re: Bogus objdump output from kernel object files?

[Sam Ravnborg]

On Tue, Feb 14, 2006 at 12:53:44PM -0800, Andrew Morton wrote:
> Chuck Ebbert <76306.1226@xxxxxxxxxxxxxx> wrote:
> >
> > On Sun, 12 Feb 2006 at 01:40:46 -0800, Andrew Morton wrote:
> > 
> >  > btw, is something up with `make foo.lst'?  It hasn't worked for me for
> >  some
> >  > time.
> >  > 
> >  > bix:/usr/src/25> make mm/vmscan.lst
> >  >   MKLST   mm/vmscan.lst
> > 
> >  Just doing 'objdump -d -r -l -j .text mm/vmscan.o' gives:
> > 
> >  mm/vmscan.o:     file format elf32-i386
> > 
> >  Disassembly of section .text:
> > 
> >  00000000 <shrink_slab>:
> >  kswapd_init():
> >  ^^^^^^^^^^^^^^
> >  This is actually at offset 0 in .init.text
> > 
> >  mm/vmscan.c:176
> >         0:       55                      push   %ebp
> >  shrink_slab():
> >  ^^^^^^^^^^^^^^
> >  OK, back to the right location.
> 
> Looks like it's a binutils problem.
> 
> 	http://sources.redhat.com/bugzilla/show_bug.cgi?id=2338
> 
> HJ said he'd try to get this fixed for the next binutils release.

I've played a little with make dir/foo.lst and it sort of seems to work
for me. But I dunno how to really check the output.
objdump spits out a warning on my amd64 due to the --adjust-vma=xxx
but that I suppose is again a binutils issue. The value calculated
generate the correct adjust factor.

The --fverbose-asm cannot omprove output of make dir/foo.lst since
the .lst file is created based on the .o file, whereas --fverbose-asm
only have impact on the file generated by gcc.

Let me know if anyone thinks something is bad with the kbuild
make dir/foo.lst functionality and I will ahve a look.

	Sam
-
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/