Bug#726970: marked as done (freebsd-glue: Broken funopen() implementation)
Your message dated Sat, 26 Oct 2013 15:18:53 +0000
with message-id <E1Va5dd-0008KK-Ri@franck.debian.org>
and subject line Bug#726970: fixed in freebsd-glue 0.1.12
has caused the Debian Bug report #726970,
regarding freebsd-glue: Broken funopen() implementation
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
726970: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726970
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: freebsd-glue
Source-Version: 0.1.11
Severity: important
Hi,
The funopen() implementation in this package uses nested functions to
wrap the argument hooks, but it returns a FILE structure pointing to
those nested functions and their references to arguments from the
stack, to be accessed outside of the function lexical scope, which is
just wrong. I've not tested if this currently breaks, but this is
explicitly stated as broken usage.
In 2011 I started some draft code to add funopen() support to libbsd,
but left it aside given the various issues with the interface. I've
just finished and polished a full implementation, and pushed to libbsd's
git master, it will be included in 0.7.0.
Regards,
Guillem
--- End Message ---
--- Begin Message ---
Source: freebsd-glue
Source-Version: 0.1.12
We believe that the bug you reported is fixed in the latest version of
freebsd-glue, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 726970@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Robert Millan <rmh@debian.org> (supplier of updated freebsd-glue package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Sat, 26 Oct 2013 16:09:29 +0200
Source: freebsd-glue
Binary: freebsd-glue
Architecture: source kfreebsd-amd64
Version: 0.1.12
Distribution: unstable
Urgency: low
Maintainer: GNU/kFreeBSD Maintainers <debian-bsd@lists.debian.org>
Changed-By: Robert Millan <rmh@debian.org>
Description:
freebsd-glue - Emulate a FreeBSD build environment
Closes: 726970
Changes:
freebsd-glue (0.1.12) unstable; urgency=low
.
* Fix improper allocation in funopen(). (Closes: #726970)
* Add _PATH_UFSSUSPEND.
* Add arc4random_stir() prototype (for libbsd).
* Work around broken macro argument in TAILQ_FOREACH_REVERSE_SAFE
Checksums-Sha1:
2b85c145e3c1ea835e3d3de85ded045e78c58060 1027 freebsd-glue_0.1.12.dsc
e1605643fec48f5aa4ad70be3d61433b85967b74 37817 freebsd-glue_0.1.12.tar.gz
a1ed55721dc2bd0f847b753846ca43464aa113c4 33364 freebsd-glue_0.1.12_kfreebsd-amd64.deb
Checksums-Sha256:
4d7a82d32cecce2400c600b2c3ad715141f23e61145673c3a209444dc268e6ae 1027 freebsd-glue_0.1.12.dsc
d21baac51f44e9d2d6aa6dea8b6208a7bf46ae199f9dcfd14019f1a8205ae3e4 37817 freebsd-glue_0.1.12.tar.gz
99f76861d036c313004917dcb826fd08e4503fdec53064011167bc92b674428b 33364 freebsd-glue_0.1.12_kfreebsd-amd64.deb
Files:
f9e465362b42a00c9f5707e1d9a3f85a 1027 devel extra freebsd-glue_0.1.12.dsc
5e07af44ff0d3899b8d4fabb55e2389f 37817 devel extra freebsd-glue_0.1.12.tar.gz
3771aa6361682d1cae64f13846df1781 33364 devel extra freebsd-glue_0.1.12_kfreebsd-amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/kFreeBSD)
iEYEARECAAYFAlJrzTwACgkQC19io6rUCv/h1wCdE6VP95f52N2Cls9jAXGH/plA
ey4AnjVTLOas0V9UUsFIYG+rHUAXDy3I
=lGZd
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: