On Mon, Aug 13, 2018 at 04:25:46PM +0200, Norbert Manthey wrote: > Dear Dan, > > I just split the output in one-line-scan, and also use your cgcc wrapper > by now. Furthermore, I log all calls to cgcc so that replaying single > calls is easy now. The relevant info is logged in the file > > SMATCH/smatch/smatch-preprocess.log > > However, I do not see a reason not to use the --file-output flag, in > case you are more used to that. That should simply result in my output > files being empty, but that's fine. This way, your tooling should work, > i.e. collecting all the .smatch files should behave as in case of > working with the kernel. > > If there is anything else I can help with, please let me know. I would > love to use your taint analysis for Xen as well. > Sorry for all this headache. Yeah. You don't need --fileoutput if you're using one-line-scan. But one-line-scan mixes stdout and stderr which doesn't work for Smatch. We only want stdout. I've just pushed some changes which should help a bit. And I'm attaching some scripts to run Smatch on xen. You're going to want to change the SCRIPT_DIR in build_xen_data.sh and it assumes that one-line-scan is in the ../one-line-scan/. Also you need to save the script in path/to/xen/../ Sorry, it's not very beautiful. regards, dan carpenter
Attachment:
build_xen_data.sh
Description: Bourne shell script
Attachment:
check.sh
Description: Bourne shell script