On Tue, Dec 26, 2017 at 1:44 PM, Kommuru jai shankar reddy <kommurujaishankarre...@gmail.com> wrote: > Yes, I am interested in the micro project of adding tests to the test > suite. Could you please provide suggestions on getting started to this ?
Sure. I'd suggest starting with ioctl decoders that are not shown as covered in LCOV reports, these are rather low-hanging fruits. The next thing is rarely used features that have no tests or are poorly tested, like path tracing or stack printing. It would be also benefitical to add some tests that cover some not previously test-covered aspects of strace's behaviour, like daemonized tracer, but in order to do that properly, some understanding of the strace internal workings is needed, and it might be difficult at first. The tests themselves reside in tests directory. The make target of interest is "make check", and you might be interested in --enable-code-coverage configuration option. Note also that code that is not covered by tests is more likely to contain errors (especially if it is some obscure ioctl one rarely cares about), so do not hesitate to fix it in case discrepancies between kernel's and strace's interpretation of syscall arguments are observed. > On Mon, Dec 25, 2017 at 11:49 PM, Eugene Syromyatnikov <evg...@gmail.com> > wrote: >> >> On Mon, Dec 25, 2017 at 5:06 PM, Kommuru jai shankar reddy >> <kommurujaishankarre...@gmail.com> wrote: >> > Hello, >> > I'm jaya shankar,. Computer science student of national institute >> > of >> > technology andhra pradesh, India >> > I have used strace for my mini project for tracing system calls of >> > malware >> > executables and it helped me a lot. >> > I want to contribute to the community and apply as student for GSOC >> > 2k18. >> > I'm having knowledge of kernel, C, git and basics of networking. >> > So, it would be great if any one suggest me some tasks for micro >> > projects >> > for gsoc, some bugs to fix for a beginner like me. >> >> Thank you for showing interest in strace. >> >> Please take a look at [1], [2], and [3] as starting points. As Chen >> JingPiao also noted recently [4], there is an ongoing effort to add >> netlink protocol decoding support to strace, which may be of interest, >> taking in account aforementioned background. >> >> If you have any specific questions, don't hesitate to ask. >> >> [1] >> https://sourceforge.net/p/strace/wiki/Guide%20for%20new%20contributors/ >> [2] https://sourceforge.net/p/strace/wiki/Microprojects/ >> [3] https://sourceforge.net/p/strace/wiki/FeatureRequests/ >> [4] https://sourceforge.net/p/strace/mailman/message/36168713/ >> >> -- >> Eugene Syromyatnikov >> mailto:evg...@gmail.com >> xmpp:esyr@jabber.{ru|org} >> >> >> ------------------------------------------------------------------------------ >> 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 > > > > > -- > Thanks > > K.jaishankar reddy > > > ------------------------------------------------------------------------------ > 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 > -- Eugene Syromyatnikov mailto:evg...@gmail.com xmpp:esyr@jabber.{ru|org} ------------------------------------------------------------------------------ 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
