On Sun, Mar 25, 2001 at 09:21:56AM +1000, Keith Owens wrote:
> On Sat, 24 Mar 2001 22:17:58 +0100,
> Jan-Benedict Glaw <firstname.lastname@example.org> wrote:
> >./elf2ecoff /home/jbglaw/kernel_src/work/mips_linux/linux/vmlinux
> >vmlinux.ecoff -a
> >Non-contiguous data can't be converted.
> > 17 .modinfo 00000018 ffffffff802730a0 ffffffff802730a0 001700a0
> > 2**2
> > CONTENTS, ALLOC, LOAD, READONLY, DATA
> This may not be relevant but vmlinux should not have a .modinfo
> section. .modinfo is only created when code is compiled with -DMODULE
> so why is it in vmlinux?
> There was a recent change to the attributes of .modinfo, from CONTENTS,
> READONLY to CONTENTS, ALLOC, LOAD, READONLY, DATA, this change was to
> remove gcc warning messages. insmod treats sections .modinfo and
> .modstring as special cases and turns off the SHF_ALLOC flag, elf2ecoff
> might need special processing for these sections.
The .modinfo section gets into vmlinux through drivers/tc/tc.o where it
gets created because include/asm-mips/dec/tcmodule.h defines the cpp
symbol MODULE; <linux/module.h> gets included after that and believing
this is a module compilation puts some stuff into .modinfo.