Menu
▾
▴
[LTP] LTP testcase compilation errors
|
From: Edwin V. <eva...@us...> - 2008-10-15 18:42:23
|
Hello, I get compilation errors when compiling LTP-full-20080930 version on s390x systems. Here's the identification of the system Linux FP3 2.6.16.21-0.8-default #1 SMP Mon Jul 3 18:25:39 UTC 2006 s390x s390x s390x GNU/Linux It'll be great if you could answer my questions below the questionable paragraphs. cc -Wall -I../../include -g -Wall -I../../../../include -Wall ptrace06.c -L../../../../lib -lltp -o ptrace06 ptrace06.c:49: error: invalid application of âsizeofâ to incomplete type âstruct pt_regsâ.. ptrace06.c:50: error: invalid application of âsizeofâ to incomplete type âstruct pt_regsâ.. ptrace06.c:51: error: invalid application of âsizeofâ to incomplete type âstruct pt_regsâ.. ptrace06.c:52: error: invalid application of âsizeofâ to incomplete type âstruct pt_regsâ.. ptrace06.c:73: error: invalid application of âsizeofâ to incomplete type âstruct pt_regsâ.. ptrace06.c:74: error: invalid application of âsizeofâ to incomplete type âstruct pt_regsâ.. ptrace06.c:75: error: invalid application of âsizeofâ to incomplete type âstruct pt_regsâ.. ptrace06.c:76: error: invalid application of âsizeofâ to incomplete type âstruct pt_regsâ.. make[4]: *** [ptrace06] Error 1 make[4]: Leaving directory `/test_cases/ltp-full-20080930/testcases/kernel/syscalls/ptrace' make[3]: *** [all] Error 2 make[3]: Leaving directory `/test_cases/ltp-full-20080930/testcases/kernel/syscalls' make[2]: *** [all] Error 2 make[2]: Leaving directory `/test_cases/ltp-full-20080930/testcases/kernel' make[1]: *** [all] Error 2 make[1]: Leaving directory `/test_cases/ltp-full-20080930/testcases' make: *** [all] Error 2 I tried to add the struct pt_regsa manually but that too didn't work. so I added the ifdef/endif statement to ptrace06.c as the same code was found in ptrace04.c and the code was branching off to the else statement which is test not supported for your arch. so can you please point out to me what we need to do to allow ptrace06.c to work. B) When running the testcase for 3hrs I get the following errors. inotify02 inotify02....... io_submit01 run-io_submit.sh ..... shmem_test_06 shmem_test_06 float_exp_log cd $LTPROOT/testcases/bin; float_exp_log -v Checking the website http://voxel.dl.sourceforge.net/sourceforge/ltp/ltp-full-20080930_results_kernel-2.6.18-8.el5_architecture-x86_64.html for this errrors I see inotify02 and io_submit01 are known errors. when I investigated why float_exp_log didn't run I found that files i.e log_inp.ref, exp_inp.ref, log10_inp.ref, frexp_inp.ref, hypot_inp.ref, ldexp_inp.ref,etc.was missing in the directory /test_cases/ltp-full-20080930/testcase/bin C) I still need to debug shmem_test_06 problem but thought of letting you guys know of the errors. If you can let me know what is the problem, it'll be greatly appreciated.. <<<test_start>>> tag=shmem_test_06 stime=1224022367 cmdline=" shmem_test_06" contacts="" analysis=exit initiation_status="ok" <<<test_output>>> ERROR [line: 205] shmat failed - return: 0xffffffffffffffff: Invalid argument shmem_test_06: IPC Shared Memory TestSuite program mykey to uniquely identify the shared memory segment 0x330e03e2 Get shared memory segment (1048576 bytes) Attach shared memory segment to process Shared memory segment address : 0x0x20000000 Index through shared memory segment ... mykey to uniquely identify the shared memory segment 0x340e03e2 Get shared memory segment (1048576 bytes) Attach shared memory segment to process Shared memory segment address : 0x0x30000000 Index through shared memory segment ... mykey to uniquely identify the shared memory segment 0x350e03e2 Get shared memory segment (1048576 bytes) Attach shared memory segment to process Shared memory segment address : 0x0x48000000 Index through shared memory segment ... mykey to uniquely identify the shared memory segment 0x360e03e2 Get shared memory segment (1048576 bytes) Attach shared memory segment to process Shared memory segment address : 0x0x50000000 Index through shared memory segment ... mykey to uniquely identify the shared memory segment 0x370e03e2 Get shared memory segment (1048576 bytes) Attach shared memory segment to process Shared memory segment address : 0x0x60000000 Index through shared memory segment ... mykey to uniquely identify the shared memory segment 0x380e03e2 Get shared memory segment (1048576 bytes) Attach shared memory segment to process Shared memory segment address : 0x0x70000000 Index through shared memory segment ... mykey to uniquely identify the shared memory segment 0x390e03e2 Get shared memory segment (1048576 bytes) Attach shared memory segment to process <<<execution_status>>> duration=0 termination_type=exited termination_id=255 corefile=no cutime=18 cstime=4 <<<test_end>>> Thanks, Edwin |