Bug 353346

Summary: WARNING: unhandled amd64-darwin syscall: unix:330
Product: [Developer tools] valgrind Reporter: Graham Leggett <minfrin>
Component: generalAssignee: Rhys Kidd <rhyskidd>
Status: RESOLVED DUPLICATE    
Severity: crash CC: rhyskidd
Priority: NOR    
Version: 3.10 SVN   
Target Milestone: ---   
Platform: macOS (DMG)   
OS: macOS   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Graham Leggett 2015-09-29 22:57:26 UTC
When an attempt is made to run Valgind on MacOSX v10.10 to debug Apache httpd, the following warning is output in an infinite loop, rendering the machine unusable:

--53395-- WARNING: unhandled amd64-darwin syscall: unix:330
==53395==    at 0x100AA475A: __sigwait (in /usr/lib/system/libsystem_kernel.dylib)
==53395==    by 0x100BBB8CC: sigwait (in /usr/lib/system/libsystem_pthread.dylib)
==53395==    by 0x1007B831A: apr_signal_thread (signals.c:383)
==53395==    by 0x100220588: child_main (event.c:2626)
==53395==    by 0x10021FE9E: make_child (event.c:2710)
==53395==    by 0x10021F7DE: startup_children (event.c:2781)
==53395==    by 0x10021DD36: event_run (event.c:3142)
==53395==    by 0x100025F04: ap_run_mpm (in /tmp/httpd-trunk/bin/httpd)
==53395==    by 0x10000FCAC: main (main.c:800)
--53395-- You may be able to write your own handler.
--53395-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--53395-- Nevertheless we consider this a bug.  Please report
--53395-- it at http://valgrind.org/support/bug_reports.html.

At the very least there needs to be a way to suppress this message, or to display this message just once.


Reproducible: Always

Steps to Reproduce:
Use the Apache httpd-test framework and run the httpd-test suite against httpd trunk through valgrind as follows:

t/TEST -d valgrind

Valgrind eventually becomes unresponsive, and you have to kill it with -9.


Actual Results:  
Warning in an infinite loop.


Expected Results:  
No warning, or just one warning.
Comment 1 Rhys Kidd 2015-10-02 05:31:12 UTC
This is a known bug report in relation to sigwait() on OS X, refer bz#211372.

*** This bug has been marked as a duplicate of bug 211372 ***