From owner-freebsd-current Sat Apr 4 01:30:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA21774 for freebsd-current-outgoing; Sat, 4 Apr 1998 01:30:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA21768 for ; Sat, 4 Apr 1998 01:30:35 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id LAA04920; Sat, 4 Apr 1998 11:28:00 +0200 (CEST) To: =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= cc: Peter Wemm , current@FreeBSD.ORG Subject: Re: Working patch *with* splhigh() (Was Re: More info RE: X slowdown in -current) In-reply-to: Your message of "Sat, 04 Apr 1998 13:15:48 +0400." <19980404131548.12530@nagual.pp.ru> Date: Sat, 04 Apr 1998 11:28:00 +0200 Message-ID: <4918.891682080@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG All those negative values still look like stack garbage to me... I would not expect your window manager to need a timeout in the select anyway, so still think things are ok in select & poll. It must be some other bit of my change which kills it, I'm suspecting nanosleep() right now... I hope you can find time to try the patch I just posted... Poul-Henning -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message