Hi,

   Thanks for your help. I tried to run Valgrind with "--tool=none"
option, but the problem remains. And I also found that the http server
did not corrected start up under Valgrind.

   When I execute the command "valgrind --tool=none ./bin/httpd -k
start", the server reports an error: "unhandled syscall: 330". Then
the server keeps reporting a warning: "Warning: unhandled socketcall
0x12". Meanwhile, the daemon processes are missing(in the normal
execution, there will be 5 daemon processes of httpd).

   So I think maybe it is the unhandled syscall or the unhandled
socketcall that fails the starting up of http server, which in turn
causes the timeout problem. Is that true and how to fix them?

   Thank you very much!

---
zhouxu

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users

Reply via email to