However, a better way of finding the caller (thanks Manfred!) if to use -m
option of insmod. This shows all the eddresses I need so I discovered that
the caller is bfs_find_entry() and after I looked at it I said in my heart
"behold, this is bad - needs rewriting".
But now the morning has started so I am back to real work and will
continue this investigation this evening at home.
Thanks to all who replied!
------
Tigran A. Aivazian | http://www.sco.com
Escalations Research Group | tel: +44-(0)1923-813796
Santa Cruz Operation Ltd | http://www.ocston.org/~tigran
On Thu, 21 Oct 1999, Keith Owens wrote:
> On Thu, 21 Oct 1999 08:31:30 +0100 (BST),
> Tigran Aivazian <tigran@sco.COM> wrote:
> >the address f881cfe3 probably lies within bfs.o's text section but I can't
> >verify it as /proc/ksyms doesn't show where the module is loaded (btw,
> >isn't *this* alone a bug? /proc/ksyms shows text/rodata addresses on my
> >machine at home i586 but not this one SMP/i686.
>
> If you mean lines like these in /proc/ksyms
>
> c404c000 __insmod_vfat_O/lib/modules/2.3.19/fs/vfat.o_M37FC4F1F_V131859 [vfat]
> c404c050 __insmod_vfat_S.text_L8062 [vfat]
> c404dfe0 __insmod_vfat_S.rodata_L712 [vfat]
> c404e400 __insmod_vfat_S.data_L336 [vfat]
>
> Those are created by modutils 2.3 to help find modules in storage.
> Without those lines, you only see the symbols that a module exports and
> if a module exports no symbols then it is effectively invisible in
> /proc/ksyms. But you need modutils 2.3.1 or better to get the extra
> __insmod lines, at a guess you have different versions of modutils on
> each machine.
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/