From:	eplmst AT lu DOT erisoft DOT se (Martin Stromberg)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: posix threads with djgpp
Date:	26 Jan 2000 16:25:42 GMT
Organization:	Ericsson Erisoft AB, Sweden
Lines:	20
Message-ID:	<86n766$aj$1@antares.lu.erisoft.se>
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 1000126143401 DOT 6180M-100000 AT is>
NNTP-Posting-Host:	spica-144.lu.erisoft.se
X-Newsreader:	TIN [version 1.2 PL2]
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Eli Zaretskii (eliz AT is DOT elta DOT co DOT il) wrote:
: This latter aspect is not a problem in the DJGPP case, because signals in 
: general, and timers in particular, are deferred until the system call 
: returns.  This is because the DJGPP signal machinery is based on 
: triggering an exception in such a way that it only happens when the 
: program is in protected mode and touches some of its data.

: The price for this is that if a program is parked inside a DOS call, like 
: if it reads from the keyboard, the signals (and threading that is based 
: on SIGALRM) are not delivered until the DOS call returns.  So, for 
: example, if you spawn a subsidiary program, threading stops until the 
: child program returns.

This is interesting. What would happen in the DOZE calls if the signal
machinery invalidated CS instead of DS?


Pettersson, Symphony 8,

							MartinS

- Raw text -