Bug 306235

Summary: unhandled syscall: 429
Product: [Developer tools] valgrind Reporter: 4ertus2 <4ertus2>
Component: cachegrindAssignee: Paul Floyd <pjfloyd>
Status: RESOLVED FIXED    
Severity: minor CC: emaste, jseward, pjfloyd, tom
Priority: NOR    
Version First Reported In: 3.7.0   
Target Milestone: ---   
Platform: FreeBSD Ports   
OS: FreeBSD   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description 4ertus2 2012-09-04 08:08:36 UTC 
--2468-- WARNING: unhandled syscall: 429
==2468==    at 0x40782CC: _sigwait (in /lib/libc.so.7)
==2468==    by 0x36E1840: sigwait (in /lib/libthr.so.3)
==2468==    by 0x47046B: XXX::SomeFunc(void*) (xxxxxxxxx.cpp:226)
==2468==    by 0x36DD597: ??? (in /lib/libthr.so.3)
--2468-- You may be able to write your own handler.
--2468-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--2468-- Nevertheless we consider this a bug.  Please report
--2468-- it at http://valgrind.org/support/bug_reports.html.


In context of
[code]
int sig;
sigwait(&sigs, &sig);
switch(sig)  { ... }
[/code]

% uname -a
FreeBSD localhost 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #3: Fri Aug 10 00:17:31 MSK 2012     root@localhost:/usr/obj/usr/src/sys/KERNEL  amd64
Comment 1 Julian Seward 2013-03-01 08:55:15 UTC 
We need to forward this to the FreeBSD port maintainer(s).  Any idea how
to do that?
Comment 2 4ertus2 2013-03-01 09:31:57 UTC 
Valgrind package description from FreeBSD ports has 3 links:

Valgrind was initially ported to FreeBSD by
Doug Rabson (http://www.rabson.org/).

WWW: https://bitbucket.org/stass/valgrind-freebsd/overview
WWW: http://www.valgrind.org/

The best way I think is to pull request via https://bitbucket.org/stass/valgrind-freebsd/pull-requests. I'll ask them.
Comment 3 Tom Hughes 2013-03-01 09:47:59 UTC 
Well as it's a bug rather than a patch I'd suggest https://bitbucket.org/stass/valgrind-freebsd/issues to open an issue rather than a pull request.
Comment 4 Ed Maste 2019-01-03 15:44:35 UTC 
Current home for Valgrind on FreeBSD is https://github.com/freebsdfoundation/valgrind

Work to commit the FreeBSD support upstream is in progress.
Comment 5 Paul Floyd 2020-06-05 13:11:02 UTC 
This is implemented with a regtest.
Comment 6 Paul Floyd 2020-10-07 08:44:55 UTC 
A similar item was created in the FreeBSD Bugzilla
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234045

The patch was merged some time ago
https://github.com/paulfloyd/freebsd_valgrind/commit/aa5a85e4b37bade33990159b0f8e065e9096131e

Update your ports tree and install valgrind/valgrind-dev from there.