lkcd
[Top] [All Lists]

Re: Module support

To: lkcd@xxxxxxxxxxx
Subject: Re: Module support
From: "Andreas Herrmann" <AHERRMAN@xxxxxxxxxx>
Date: Wed, 18 Jul 2001 15:56:36 +0200
Importance: Normal
Sender: owner-lkcd@xxxxxxxxxxx
(Sorry for the late reply, I was on vacation until yesterday.)


 Luc Chouinard wrote:
>Jyunji, Andreas Herrmann has been doing some work on a feature like this
>one for lcrash. I'm not sure how complete Andreas's work is at this
>time. I know there was also some legal issues involved in releasing that
>work to the group.
>
>Andreas, any status ?

I regard my work on this subject as finished. Of course, as always
there is plenty of room for minor enhancements.
The actual show stopper is the legal clearance issue.
I can just say, we will check in the new stuff as soon as we have
the legal clearance to do so. I know this situation is not
satisfactory, but I can't help it.
When we do the check-in we will tag the old lkcd version, so everybody
can play around with the new commands. And if anybody dislikes the
new stuff, an easy fallback to the old version can be made.

Michael Holzheu has given already some information about the new
stuff. Let me give some additional explanation.

The new command "module" helps to investigate module structures in
the dump. The starting point is the variable module_list of the
kernel. It is the anchor of a chained list of structures of kind
"struct module". Some information, received from these structs,
can be displayed by using the "module" command.

The second new command is "symtab". It is used for handling of
multiple symbol tables. You can add, remove and show information of
symbol tables. The command can automatically detect the segment
offsets when symbol tables for modules are loaded. It uses a mechanism
like ksymoops to detect the offsets.
By the way, lcrash creates an additional symbol table "ksymtab" during
startup. It contains all exported kernel symbols. From this table the
segment offsets of modules are extracted. But the exploitation of this
symbol table can and should be improved to use it as a default
table when searching for symbols during "dis", "trace" etc.

The advantages in having multiple symbol tables are:
- findsym, dis, trace, strace, whatis commands can find symbol
  names of functions located in modules (iff symbol tables were
  previously added)
- symbol tables can be removed and again added without restart of
  lcrash - I find it quite comfortable, if wrong table was loaded or
  while playing around with a live system and different module
  versions

So, I ask you to be patient until we have our internal o.k. to check
in the stuff.

Regards,

Andreas

--
Linux for eServer Development
Tel :  +49-7031-16-4640
Notes mail :  Andreas Herrmann/GERMANY/IBM@IBMDE
email :  aherrman@xxxxxxxxxx



Jyunji Kondo <j-kondo@xxxxxxxxxxxxxxx> on 07/17/2001 05:52:45 AM

Please respond to j-kondo@xxxxxxxxxxxxxxx

To:   lkcd@xxxxxxxxxxx
cc:
Subject:  Re: Module support





> Jyunji, Andreas Herrmann has been doing some work on a feature like this
> one for lcrash. I'm not sure how complete Andreas's work is at this
> time. I know there was also some legal issues involved in releasing that
> work to the group.

That's sounds nice.

> Andreas, any status ?

Please let me know any pointers about this work?
Thanks.




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