>>> About utrace().. i have never tested it, just read about it, and >> I agree... but look into the future, be prepared. There are tons of >> papers and discussions against ptrace. Ptrace is history... sthg new >> is needed. Lot of new things are needed, otherwise linux is going to >> die!
> linux must die. long life plan9 woww... another thing where we agree :) Well, actually linux would be more than fine if they would be open for evolution, but it seems to be industry driven, and that freezes. It is like you send a child who is an absolute musical talent, to study medicine, or even worst engineering... There are lot of talented (this time talent in IT :) ) people involved in linux kernel, but I saw so many things discouraged like "fibril", brain f*ing scheduler, etc.. that for some reason were not overlapping at all the taste area of main people like Linus Tovarlds or Ingo Molnar. I would be happy if people like them would be present here, or other mailing list, where the agony of linux is mentioned in one or other context. >>> All the ptrace() antidebug tricks should not be catched using >>> utrace().. > i fully agree with you, but the debugging architecture in r2 is not yet > fully implemented, but works for most basic things, so you should be > able to check the code and ping me for any question you have. > But I would prefer to wait utrace() gets mainstream, things can change > and is better not to repeat the work twice. I did not want to convince you that you should be prepared with code, just be prepared with ideas, and probably to be prepared to know what others or doing around utrace, eventually try to enforce your ideas, needs etc. -- rgrds, mobi phil being mobile, but including technology http://mobiphil.com _______________________________________________ radare mailing list [email protected] http://lists.nopcode.org/listinfo.cgi/radare-nopcode.org
