[eresi-dev] A new cycle of ERESI (important message to read)

[zadig]

Hello everybody,

Since nobody answered yet, I will begin.
First let me introduce mysefl since probably very few people have heard 
about me:
I started working on elfsh when v0.5 was published. My aim was (and 
still is) to port it on BeOS systems. Some of my changes have been 
commited in the tree, and other ones are still "private".

My involvment in the project is and will probably always be from time 
to time: I would like to do much more than what I do, but free time is 
a critical resource for me! The last years I spent about 6/7 weeks of 
night time per year to continue the port. The rest of the time I just 
sync my local devs with the tree.

However I think that this is quite interesting for the project maturity 
because running eresi on BeOS already showed issues that where not 
obvious on all other unixes. 

So I can not guarantee that I will work x time on the project, but I 
will certainly continue to work on the following part:

1- libelfsh: 
Especially injection of global objects addressed via the got. I have 
something almost working. This seem to be the last thing to do to get a 
fully working injection on BeOS.

2- kernsh:
I did not look at it yet but this seems a very interesting feature to 
add to BeOS.

3-e2dbg
I started to port it but it is not working yet (I may work on it next 
week).

4- Eventually a gui: 
I think about it since quite some time. A gui to control some "classic" 
features of eresi should be great: disassembler and debugger 
epsecially. Maybe there is something already planned for this in the 
eresi roadmap.


Zadig.

PS: When I say BeOS, you should understand Zeta and Haiku (zeta-os.com, 
haiku-os.org)