After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 650078 - forkbomb building glib/tests/protocol
forkbomb building glib/tests/protocol
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: general
2.26.x
Other FreeBSD
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2011-05-13 05:31 UTC by Peter O'Gorman
Modified: 2011-05-16 18:39 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Peter O'Gorman 2011-05-13 05:31:25 UTC 
If a user has . in path (or in the case of Free BSD /bin/sh an extra : in PATH) the current working dir will be searched for executables. glib/tests has an executable named 'printf'. GNU libtool on some platforms uses printf to print strings. Linking can forkbomb on systems where this happens.

I suggest renaming the printf test to something else.

To reproduce, on Free BSD 8.2

cd /usr/ports/devel/glib20; env PATH=:$PATH gmake

It is not uncommon to end up with an accidental extra : in one's path, that this is treated as '.' by /bin/sh is a bug in /bin/sh on FreeBSD, but since forkbombing is never nice, it would be good to fix it in glib too.