Subject: port-arm32/5178: __vfork14 hangs system
To: None <gnats-bugs@gnats.netbsd.org>
From: None <Alex.Hayward@mac57.lmh.ox.ac.uk>
List: netbsd-bugs
Date: 03/19/1998 17:59:08
>Number: 5178
>Category: port-arm32
>Synopsis: Calling __vfork14 causes the system to hang completely.
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: gnats-admin (GNATS administrator)
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Mar 19 11:05:01 1998
>Last-Modified:
>Originator: Alex Hayward
>Organization:
alex @ hayward.u-net.com; alexander.hayward @ lmh.ox.ac.uk
xelah @ ferret.lmh.ox.ac.uk
>Release: NetBSD-current 19 Mar 98
>Environment:
System: NetBSD mac57.lmh.ox.ac.uk 1.3E NetBSD 1.3E (HAYWARD) #39: Thu Mar 19 14:24:17 GMT 1998 compile@mac57.lmh.ox.ac.uk:/usr/src/sys/arch/arm32/compile/HAYWARD arm32
1.3 release userland, but 1.3alpha cc1 and cc1plus and Mar 16th libs.
>Description:
Calls to __vfork14 causes a complete system hang: no keyboard response, no cursor flashing etc.
This includes old binaries that call system() (which calls vfork).
>How-To-Repeat:
Build and install a new libc. Try to read a manual page.
>Fix:
Comment out __RENAME(__vfork14) in the vfork declaration in unistd.h before building libc.
>Audit-Trail:
>Unformatted: