> 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".

The version I use is valgrind-3.7.0.SVN.

> 2) Which hardware and operating system (and version) are you using?
>   If Linux, then report the output from running "uname -a".

The operation system is Fedora 12. The output of "uname -a" is the following:
Linux localhost.localdomain 2.6.31.5-127.fc12.i686.PAE #1 SMP Sat Nov
7 21:25:57 EST

>>    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).

The output of my command "sudo valgrind --tool=none ./bin/httpd -k
start" in my platform is the following:
[zhouxu@localhost httpd-prefork]$ sudo valgrind --tool=none ./bin/httpd -k start
==3777== Nulgrind, the minimal Valgrind tool
==3777== Copyright (C) 2002-2009, and GNU GPL'd, by Nicholas Nethercote.
==3777== Using Valgrind-3.5.0 and LibVEX; rerun with -h for copyright info
==3777== Command: ./bin/httpd -k start
==3777==
httpd: Could not reliably determine the server's fully qualified
domain name, using localhost.localdomain for ServerName
--3777-- WARNING: unhandled syscall: 330
--3777-- You may be able to write your own handler.
--3777-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--3777-- Nevertheless we consider this a bug.  Please report
--3777-- it at http://valgrind.org/support/bug_reports.html.
==3777==
[zhouxu@localhost httpd-prefork]$ --3777-- WARNING: unhandled syscall: 330
--3777-- You may be able to write your own handler.
--3777-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--3777-- Nevertheless we consider this a bug.  Please report
--3777-- it at http://valgrind.org/support/bug_reports.html.
--3777-- Warning: unhandled socketcall 0x12
--3777-- Warning: unhandled socketcall 0x12
--3777-- Warning: unhandled socketcall 0x12
--3777-- Warning: unhandled socketcall 0x12

Thanks for your patient.
---
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