Date: Wed, 13 Oct 1999 11:51:36 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: PAOLO GAVA <pgava AT etrone DOT com DOT au>
cc: djgpp AT delorie DOT com
Subject: Re: critical section
In-Reply-To: <2LFM3.188$va4.4238@nsw.nnrp.telstra.net>
Message-ID: <Pine.SUN.3.91.991013115117.16702N-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Tue, 12 Oct 1999, PAOLO GAVA wrote:

> I want to execute a function that can never be interrupted.
> So I tried to disable the interrupt with CLI, but it doesn't work in fact
> the clock interrupt is still coming.

Try calling the library function disable() instead.

If that doesn't work either, post here the necessary details (which
you should have posted to begin with): under what OS does this happen,
code fragment(s) that implement the critical section, how do you know
that the interrupts are still coming, etc.