Speaking about the progress, I'd say that the main reason why it is not possible to show from time to time commitment is that each commit should provide stable or work version of program. And for now, this version provides work tool in sense of arch and abi options(with all architectures). As the tool is new sometimes it is not possible to send out patches with the small pieces of code, showing progress, because each part is quite big and needs a lot of time to implement universal and supported code for the upcoming architectures.
Concerning plan, in 1 day, I will send out the work version of syscall_dispatcher and couple of days later I am going to provide work version of command_dispatcher. Actually, I am not quite sure about ARM architectures, am I right there or not. (I mean ABI modes). Because, according to the current syscallent.h file in arm dir, there is not support for subcall in ARM EABI, is it correct? Because, in the kernel there is place for these subcalls. I am waiting for review. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Strace-devel mailing list Strace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/strace-devel
