From: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
To: <djgpp-workers AT delorie DOT com>
Subject: RE: Interaction between __dpmi_yield and signals?
Date: Mon, 22 Jan 2001 21:56:15 +0100
Message-ID: <NEBBIOJNGMKPNOBKHCGHCEPOCAAA.tim.van.holder@pandora.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-Reply-To: <7458-Mon22Jan2001223025+0200-eliz@is.elta.co.il>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id PAA25420
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> No.  There's only one timer, so setting it again nukes the first one.
Then I _really_ don't see where the problem comes from.

> Anyway, you could modify __dpmi_yield to print on the screen whether
> SIGALRM is hooked or not, and then run the program and see what
> happens.  (Be careful not to use printf or anything fancy, though.  I
> suggest simply write 0 or 1 to some point on the screen with
> farpokeb.)
Thanks, but I think I'll leave well enough alone; it works for now.
I'll investigate this further if and when a real problem shows up. At
least I'll know where to start :-)