How about allowing a user to define ones' own class in ~/.strace?
(cat ~/.strace)
classes:
- name: xattr
- syscall: setxattr
- syscall: lsetxattr
- syscall: fsetxattr
- syscall: getxattr
- syscall: listxattr
- syscall: removexattr
- name: setxattr
- syscall: setxattr
- syscall: lsetxattr
- syscall: fsetxattr
So you can do -e trace=%xattr or -e traec=%setxattr as you want.
However, I think we cannot say thie extension a microproject:-P
Masatake YAMATO
> On Thu, 15 Feb 2018 19:07:59 +0530
> Abhishek Tiwari <erabhishektiwar...@gmail.com> wrote:
>
>> Hi,
>>
>> I want to work on microproject
>>
>> extend -e trace=class syntax with new classes
>>
>>
>> I have gone through mailing list. Is following grouping ok
>>
>> {,l,f}setxattr TRACE_SETXATTR TFX
>>
>>
>> -e trace=%setxattr
>
> This is a good start, but from what I see, maybe this group is too
> small, maybe all the syscalls that deals with xattr should be a better
> idea, something like -e trace=%xattr.
>
>
> --
> Gabriel Laskar
>
> ------------------------------------------------------------------------------
> 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
------------------------------------------------------------------------------
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
