[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: rpctrace improvement -- how I'm going on
From: |
Maurizio Boriani |
Subject: |
Re: rpctrace improvement -- how I'm going on |
Date: |
Thu, 7 Jun 2001 17:32:07 +0000 |
User-agent: |
Mutt/1.3.12i |
On Wed, Jun 06, 2001 at 12:21:26AM +0000, Maurizio Boriani wrote:
> Hi all,
> I've studied and understand what rpctrace now is and how it work, so
> I'm ready to develop next things:
> * add to printed out text msg names and ids.
This is what I've do in order to improve rpctrace with msg characters names:
* I've searched out much header files in order find out if in some
structure character name is reposrted, but I ve found noone.
* I've understand that in mach and hurd structures rpc msgs are indexed
used ONLY unsigned integer.
* I've found a fine named subsystems in main hurd source directory wich
contain base unsigned integer for all subsystems rpc msgs and in some other
sources I've read which anyone of them contain 200 spaces for procedures,
functions and so on.
* In any other file I've not found hardcoded rpc unsigned integer name.
* So I think is mig which generate this number and hardcode it in
output file which will be linked whit other souces (clients and server)
* So I think two solutions:
* generate in mach and hurd build time a file in /etc (maybe
/etc/rpc) with unsigned integer name <-> character name translations.
* in rpctrace build parse file generated by mig and hardcode
translation (unsigned integer VS characters names.
What do you think? This could be right? If yes, IMHO the best solutions is firs
one (create a index file in /etc)
I'm wait for suggestions.
bye and thank you in advance
--
Maurizio Boriani -- Debian developer
http://www.debian.org/%7Ebaux/
PGP key: 0xCC0FBF8F
fingerprint => E429 A37C 5259 763C 9DEE FC8B 5D61 C796 CC0F BF8F <= fingerprint
pgpjvlQiFACQQ.pgp
Description: PGP signature