Re: "mcount" symbol in modules

["Nicolas S. Dade" <ndade@jasiri.com>]

On Tue, Dec 24, 2002 at 11:17:07PM +0100, Leonardo Macchia wrote:
> On Sun, Dec 22, 2002 at 13:00:34 +0100, Leonardo Macchia wrote:
> 
> > depmod: *** Unresolved symbols in /lib/modules/2.4.20/kernel/drivers/block/loop.o
> > depmod:         mcount
> > [...]
> 
> This problem seems to be related with "CONFIG_MCOUNT" option that is
> implied by "CONFIG_STACK_DEBUG": disabling the latter, everything works
> fine again.

gcc inserts calls to mcount() at the start and end of functions
if profiling (-p) is enabled. Normally mcount() is supposed to
record the time and the return address. But you can also use
mcount() to check that the stack has not overflowed, which
is what CONFIG_STACK_DEBUG is doing with it.

Basically you seem to be building a debug build.

-- 
-- Nicolas Dade    http://nsd.dyndns.org/    nic@jasiri.com