Re: New module loader makes kernel debugging much harder

[Keith Owens <kaos@ocs.com.au>]

On Sat, 23 Nov 2002 16:23:46 +0000, 
John Levon <levon@movementarian.org> wrote:
>On Sat, Nov 23, 2002 at 01:43:20PM +1100, Keith Owens wrote:
>
>> Only if you assume that the .text is at a known offset from the start
>> of the module.  There are multiple programs that need to know where
>> each section really is, instead of making assumptions about how a
>> module is laid out.
>
>Yes, sorry, that is what I meant.

Even for module profiling, we need section data available.

Although all module code currently goes in a single text area, there is
no guarantee that will always be the case.  In the past we have had
multiple text areas in modules (out of line lock code used its own
section for a long time) and future changes could require multiple text
sections.  To do profiling correctly, you need to know where all the
text sections are, i.e. the module loader has to publish symbols and
section data.  Loosing that data is a big step backwards.