In ltp-full-20130503 chmod02.c line 190 I believe that &buf should be just buf. This is because buf, declared at line 128, is already a pointer to the string "file contents\n" and the system function write requires as its second argument a pointer to the buffer to be written to the file "tfile". By looking to tfile I found that with &buf I got unreadable data while with buf I got "file contents" as it should be.
In sigrelse01.c line 646 the function write_pipe attempts to write MAXMESG bytes from its second argument to the pipe. MAXMESG is declared as 512 at line 149. At line 291 write_pipe is called with READY as the buffer pointer. READY is defined at line 151 as the string "ready". "ready" is only six bytes long, including the null at its end, while write_pipe attempts to transfer 512 bytes. I think this is questionable because nobody knows the contents of the other 506 bytes, you may even get a segmentation fault because the data area is shorter, depending on the implementation. I believe my comments are implementation independent, anyway I have an x86-64, with Fedora 19 and gcc 4.8.1. Best regards Vittorio ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
