>> huh? what does libmach (which takes apart executables) >> have to do with any of this? >> > Did I get the wrong impression when I perceived libmach, as released > with GoLang - cause that's where I looked - seemingly quite capable of > synthesising as well as analysing binary images?
i think you did. libmach has routines to read executables and object files (8.out and *.8) but not to write them. the programs that write them (8a, 8l, 8c, 8g) all use custom code, mainly because they have their own internal representations of the instruction stream, tailored to the kinds of annotations they need. 8l even has its own reader for *.8 files, for much the same reason. russ
