From owner-freebsd-current Mon Mar 4 11:45:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA22420 for current-outgoing; Mon, 4 Mar 1996 11:45:33 -0800 (PST) Received: from jhome.DIALix.COM (jhome.DIALix.COM [192.203.228.69]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA22415 for ; Mon, 4 Mar 1996 11:45:29 -0800 (PST) Received: from localhost.DIALix.oz.au (peter@localhost.DIALix.oz.au [127.0.0.1]) by jhome.DIALix.COM (8.7.4/8.7.3) with SMTP id DAA01144 for ; Tue, 5 Mar 1996 03:44:56 +0800 (WST) Message-Id: <199603041944.DAA01144@jhome.DIALix.COM> X-Authentication-Warning: jhome.DIALix.COM: Host peter@localhost.DIALix.oz.au [127.0.0.1] didn't use HELO protocol To: current@freebsd.org Subject: The Netscape/Linux emulator scrollbar bug exposed!!! :-) Date: Tue, 05 Mar 1996 03:44:55 +0800 From: Peter Wemm Sender: owner-current@freebsd.org Precedence: bulk Well, I'm afraid I'm going to do it.. I'm going to tell _what_ trivial bug was preventing the Netscape scrollbars being rendered when using Netscape-2.0 under the Linux emulator.. It's nothing grand, like the Motif botches, Netscape programming errors, signal emulation, select emulation, pipe write coalescing, socket code, lost Xserver events, phase of the moon, etc. :-) It's actually *unbelievably* trivial! :-) It is.. *drum roll*.... The Linux emulation of the time(2) syscall was getting an EFAULT for time(0) and returning zero instead of the correct time.... ***AAARRRGGGGHHHH!!!!*** I presume Netscape were simply calling time(0) in their main buzz-loop and once every second, they were rendering the scrollbar. Presumably the initial "last_time_rendered" variable was zero, so it was never drawn, because time(0) was returning zero.. *** SCREAM ***!! Yes, this ~10 character change is trivial enough to go into -stable.. :-) Cheers, -Peter