Date: Fri, 14 Sep 2012 13:03:11 +0200 From: Ivan Voras <ivoras@freebsd.org> To: freebsd-hackers@freebsd.org Subject: Re: Change vfork() to posix_spawn()? Message-ID: <k2v2te$ok1$1@ger.gmane.org> In-Reply-To: <035514CA-81D6-407F-A2C1-51A9FB0E3A74@cederstrand.dk> References: <035514CA-81D6-407F-A2C1-51A9FB0E3A74@cederstrand.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigBB57C1BA0D64AA99FC0B2170 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 14/09/2012 09:49, Erik Cederstrand wrote: > Hello hackers, >=20 > I'm looking through the Clang Analyzer scans on http://scan.freebsd.you= r.org/freebsd-head looking for false positives to report back to LLVM. Th= ere are quite a list of reports suggesting to change vfork() calls to pos= ix_spawn(). Example from /bin/rpc: http://scan.freebsd.your.org/freebsd-h= ead/bin.rcp/2012-09-12-amd64/report-nsOV80.html#EndPath >=20 > I know nothing about this but I can see fork and posix_spawn have been = discussed on this list previously. Is this a legitimate warning (in this = case and in general in FreeBSD base)? Currently (on 9-stable at least), posix_spawn() is implemented as a wrapper around vfork(), so I doubt replacing one with the other would do much. --------------enigBB57C1BA0D64AA99FC0B2170 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlBTDu8ACgkQ/QjVBj3/HSxuiwCffNvAgiKPU9grWind829tY9Ll EjkAn1Qw8j2WFyR61Zr4qpYY2NfEkQnf =D9gh -----END PGP SIGNATURE----- --------------enigBB57C1BA0D64AA99FC0B2170--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?k2v2te$ok1$1>