On Sat, Jun 9, 2012 at 4:06 PM, John Reiser <[email protected]> wrote: > Please tell us complete details. The information "syscall: 330" > is ambiguous, because system call numbers depend on the hardware > and on the operating system. > > 1) Which version of valgrind are you running? > Report the output from running "valgrind --version". > > 2) Which hardware and operating system (and version) are you using? > If Linux, then report the output from running "uname -a". > >> 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? > > Unhandled syscall definitely is a problem. Telling us the complete > details will make it much easier to suggest how to fix the problem(s).
Also, if not for the analysis then maybe for documentation for later reference, how are you starting apache httpd as a userland process ? I can't seem to do so. I am only able to control it via init.d start/stop scripts. I understand that you are able to run your web server normally, and that it works well, or even much faster, but how do you start it then ? Can you run the server by "./bin/httpd -k start" ? ~lImbus ------------------------------------------------------------------------------ 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
