Hi! > I'm a new user of LTP tool , my goal is to execute some system calls using > LTP and to intercept them using a kernel tracer . > > i do this example : > > /opt/ltp/runltp -q -p -l result.03.log -f > /home/jessica/LTP-test/test-syscall.txt > > the content of the test-syscall.txt file is : > #Tag Test case > #--------------------------------------- > fork01 fork01 > chdir01 symlink01 -T chdir01 > #---------------------------------------- > > the problem is that i didn't intercept the syscall fork and the syscall > chdir using my tracer in the kernel space. > > So i wanna ask : > Which processes are responsible of the execution of these system calls ? > Does this tool, i mean LTP, really execute these system calls ( fork and > chdir ) in the kernel space?
The test itself (standalone executable binary) calls the syscall to be tested. But these are not the only syscalls that the test calls you cannot write a test that calls a single syscall. You can run most of the tests directly (without the runltp script) if you execute the cmdline (marked as Test case in your example file) in the directory with the test binaries or if you add the path to your PATH. Moreover the runltp tool that runs LTP tests forks a few times before the actual test is executed. You cannot run new program without doing fork() beforehand in UNIX. So in your place, I would double check if the kernel tracing works. -- Cyril Hrubis [email protected] ------------------------------------------------------------------------------ Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
