kernprof
[Top] [All Lists]

2.4.16 kernel, 0.10.3 profiler, 2.96 gcc, insmod -> unresolved symbol mc

To: <kernprof@xxxxxxxxxxx>
Subject: 2.4.16 kernel, 0.10.3 profiler, 2.96 gcc, insmod -> unresolved symbol mcount
From: "Cameron, Steve" <Steve.Cameron@xxxxxxxxxx>
Date: Tue, 27 Nov 2001 11:18:01 -0600
Sender: owner-kernprof@xxxxxxxxxxx
Thread-index: AcF3Z3feiELzOSKXRYWjYKvrGNqYTw==
Thread-topic: 2.4.16 kernel, 0.10.3 profiler, 2.96 gcc, insmod -> unresolved symbol mcount
Hi,  
(please cc me directly as I'm not subscribed, if it's not too much
trouble.)

I gather this has been seen before, but under different
circumsntatnces.  I couldn't find a solution though.  I 
looked through the archives a bit, (long enough to see 
I'm not the only one with this problem) and through
the FAQ.

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.)

my gcc is 2.96  (this is redhat 7.2)

Any ideas?

>From the web page, I see that this exact bug was fixed
in a previous version of the profiler... I guess it has
come back?

Thanks, 

-- steve




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