Subject: Re: unproven-pthreads problem (?) Virtual timer expired
To: Olaf Seibert <rhialto@polderland.nl>
From: Jason R Thorpe <thorpej@zembu.com>
List: current-users
Date: 08/10/2000 07:08:54
On Thu, Aug 10, 2000 at 12:41:10PM +0200, Olaf Seibert wrote:

 >   8439 python   GIO   fd 1 wrote 22 bytes
 >        "Running command: make
 >        "
 >   8439 python   RET   write 22/0x16
 >   8439 python   CALL  __vfork14
 >   8440 python   RET   fork 0
 >   8440 python   CALL  execve(0x1604f6676,0x1ffffe980,0x1ffffef78)
 >   8440 python   NAMI  "/bin/sh"
 >   8440 sh       EMUL  "netbsd"
 >   8439 python   RET   __vfork14 8440/0x20f8
 >   8439 python   CALL  wait4(0x20f8,0x1ffffe9a0,0x1,0)
 >  
 > Hm.. can it be that python actually calls __vfork14() while libpthread
 > actually wraps plain vfork()? I'll have a look...

Yes, unproven-pthreads needs to handle the renamed versions of all the
calls it cares about, too.

-- 
        -- Jason R. Thorpe <thorpej@zembu.com>