On Tue, Sep 7, 2010 at 5:18 AM, Caspar Zhang <[email protected]> wrote:
> Hi all,
>  When I run testcases/network/nfs/nfsstress/ test, I found sometimes the
> test failed due to buffered I/O, in detail, for example, there are the 
> following
> lines in make_tree.c :
>
> 544     numchar[0] = sprintf(prog_buf,
> 545                 "main()\n{\n\t printf(\"hello world\");\n}\n");
>
> sometimes the generated .c file will be:
> ^...@ain() // <- strange ASCII char '^@' appears instead of 'm'
> {
>        printf("hello world");
> }
>
> And running with this .c file will cause error.
>
> That is to say, string 'prog_buf' gets a mistake during sprintf. And there're
> somewhere else using buffered I/O in this test as well. Do we have an
> unbuffered solution to this test?

That seems a bit odd. Is the NFS mount/server TCP or UDP?

Thanks,
-Garrett

------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list

Reply via email to