Help in Understanding the Strace Code Base.

Alangi Derick alangiderick at gmail.com
Sat Feb 21 07:16:31 UTC 2015


On 2/20/15, Dmitry V. Levin <ldv at altlinux.org> wrote:
> On Thu, Feb 19, 2015 at 11:02:42PM +0100, Alangi Derick wrote:
>> Hello,
>>     I will  really like to understand the Strace code base. Lately i have
>> been facing some difficulties on how to work around the code based. So
>> please if there are some tutorials that i can work with or if there is
>> some
>> where help can come from, then that will be fine.
>
> Well, strace is a regular free software.  It's build system is based on
> GNU Autoconf and GNU Automake, xlat/*.h files are generated by bootstrap
> script from appropriate xlat/*.in files automatically using xlat/gen.sh
> shell script.  Automated tests are in tests/ subdirectory, you can use
> "make check" to run them.  The code itself is written in C.  If you are
> interested in hairy ptrace-related stuff, consider reading
> README-linux-ptrace first.  For better understanding of strace,
> I'd recommend browsing internet for various strace use cases.
>
> There are two points where one can easily find a room for improvement.
> The first is extensible decoders, e.g. ioctl syscall decoder.
> The second is test suite.
>
>
> --
> ldv
>
OK, thanks Dmitry. From my understanding of your last post, i will
have to read on I/O Control(ioctl()) system call then i dive into the
ioctl syscall decoder at once. I will look at how it is implemented
and also understand the trend of development of strace now. Then i
will start contibuting.
          Thanks.




More information about the Strace-devel mailing list