From: SourceForge.net <no...@so...> - 2009-05-04 15:18:01
|
Bugs item #2786665, was opened at 2009-05-04 17:17 Message generated for change (Tracker Item Submitted) made by mischajonker You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=103382&aid=2786665&group_id=3382 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Testcases Group: System Calls Status: Open Resolution: None Priority: 5 Private: No Submitted By: Mischa Jonker (mischajonker) Assigned to: Nobody/Anonymous (nobody) Summary: sync_file_range01 fails on MIPSEL32 Initial Comment: It probably fails because the testcase is doing a syscall directly (without using glibc). For MIPS32, it is important that the 64-bit arguments are 64-bit aligned. Glibc solves this by adding a dummy variable after the 'fd' argument: int sync_file_range (int fd, __off64_t from, __off64_t to, unsigned int flags) { return INLINE_SYSCALL (sync_file_range, 7, fd, 0, __LONG_LONG_PAIR ((long) (from >> 32), (long) from), __LONG_LONG_PAIR ((long) (to >> 32), (long) to), flags); } <<<test_start>>> tag=sync_file_range01 stime=1240582190 cmdline="sync_file_range01" contacts="" analysis=exit initiation_status="ok" <<<test_output>>> sync_file_range01 1 PASS : expected failure - errno = 9 : Bad file descrip sync_file_range01 2 PASS : expected failure - errno = 29 : Illegal seek sync_file_range01 3 FAIL : call succeeded unexpectedly sync_file_range01 4 PASS : expected failure - errno = 22 : Invalid argumen sync_file_range01 5 FAIL : call succeeded unexpectedly <<<execution_status>>> duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=1 <<<test_end>>> ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=103382&aid=2786665&group_id=3382 |