kernprof
[Top] [All Lists]

Re: 2.4.16 kernel, 0.10.3 profiler, 2.96 gcc, insmod -> unresolved symbo

To: "Cameron, Steve" <Steve.Cameron@xxxxxxxxxx>, <kernprof@xxxxxxxxxxx>
Subject: Re: 2.4.16 kernel, 0.10.3 profiler, 2.96 gcc, insmod -> unresolved symbol mcount
From: "John Hawkes" <hawkes@xxxxxxx>
Date: Thu, 29 Nov 2001 14:33:49 -0800
References: <45B36A38D959B44CB032DA427A6E10640167CF00@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: owner-kernprof@xxxxxxxxxxx
From: "Cameron, Steve" <Steve.Cameron@xxxxxxxxxx>
> Doing "insmod anymodule" I get
>
> unresolved symbol mcount
>
> (Though all my looking through the code, I can't see how
> mcount can possibly be unresolved,
> (e.g. nm vmlinux shows it as "T", in the text)
>
> I have patched 2.4.16 with the profiler patch 0.10.3,(for 2.4.14)
> (small mismatch in sched.c, but no big deal to fix, and some
> rejects in ia64 and sparc land that I ignored, as I'm
> in i386 land.)

I've just done pretty much the same thing -- 0.10.4 massaged to patch
2.4.16 -- and I'm not seeing this same insmod problem.  Are you sure you
compiled your kernel with CONFIG_MCOUNT?

John Hawkes
hawkes@xxxxxxx



<Prev in Thread] Current Thread [Next in Thread>