On Mon, 21 Aug 2000, Bill Studenmund wrote:

: > loading `.sdata2': addr = 0xe9209578, size = 0
: > modload: error loading buffer: Cannot allocate memory
: > 
: > Um... what's .sdata2? (I wasn't aware that was even a legal name for a
: > segment.) Why are we having difficulty allocating memory for a zero-
: > size buffer?

: Another option might be "objcopy -R sdata2 <lkm> <new lkm name>".

This may be a good stopgap.  However, I'd definitely want to find out why
modload is attempting to load that section of size 0.  `I got a baaaaaad
feeling about this....'

: Oh, .sdata2 is a ppc-specific section name. I'm not sure what it's good
: for.

It's used for -mdata=eabi, which is a slightly different way of referencing
`far' data (that's probably the best way I can describe it without going
into the machine-specific guts).  The EABI data reference generation code is
in gcc/config/rs6000/svr4.h.

Since the code isn't compiled -mdata=eabi, it isn't putting anything in the
.sdata2 section (even though the section is there).

-- 
-- Todd Vierling <tv@wasabisystems.com>  *  http://www.wasabisystems.com/
-- Speed, stability, security, and support.  Wasabi NetBSD:  Run with it.