delorie.com/archives/browse.cgi | search |
From: | "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be> |
To: | <djgpp-workers AT delorie DOT com> |
Subject: | Interaction between __dpmi_yield and signals? |
Date: | Sun, 21 Jan 2001 12:47:45 +0100 |
Message-ID: | <NEBBIOJNGMKPNOBKHCGHGENPCAAA.tim.van.holder@pandora.be> |
MIME-Version: | 1.0 |
X-Priority: | 3 (Normal) |
X-MSMail-Priority: | Normal |
X-Mailer: | Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) |
Importance: | Normal |
X-MimeOLE: | Produced By Microsoft MimeOLE V5.50.4133.2400 |
X-MIME-Autoconverted: | from quoted-printable to 8bit by delorie.com id GAA24136 |
Reply-To: | djgpp-workers AT delorie DOT com |
I ran across the follwing issue: the Smalltalk testsuite has a test for its delay mechanism, which aborted due to a SIGALRM, even though a signal handler was properly installed. I tracked the problem to a function called 'relinquish', which uses select() to relinquish control for a short time. Using sleep() gave the same result, probably because both called __dpmi_yield(). Changing the relinquish() function to do nothing at all on DJGPP does work, however. I just don't see why calling __dpmi_yield would cause a SIGALRM not to be delivered properly.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |