Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!caip!princeton!allegra!ulysses!mhuxr!mhuxn!ihnp4!inuxc!pur-ee!uiucdcs!convex!trsvax!kevin
From: kevin@trsvax
Newsgroups: net.micro.pc
Subject: Re: Interrupts and Microsoft C
Message-ID: <53500028@trsvax>
Date: Sat, 31-May-86 15:25:00 EDT
Article-I.D.: trsvax.53500028
Posted: Sat May 31 15:25:00 1986
Date-Received: Wed, 4-Jun-86 19:34:51 EDT
References: <674@hou2f.UUCP>
Lines: 22
Nf-ID: #R:hou2f.UUCP:674:trsvax:53500028:000:891
Nf-From: trsvax!kevin    May 31 14:25:00 1986


> I have an interrupt service routine which is linked with
> my Microsoft 'C' application program. When the program is started
> it installs the pointer to the service routine in the vector table.
> As soon as the first interrupt is generated I get a stack overflow 
> message on the screen and the system hangs. If I disable the external
> interrupt source everything works fine. Sounds like a problem in the 
> interrupt service routine.

Try compiling the 'C' module with stack probes removed (the /Gs option,
I think).  The stack pointer as MSC is comparing it is probably not
what is actually passed by the interrupt service routine.

You might also have problems with what DS is set to, depending on
what model you're using.

I had a similar problem doing a routine run off the timer interrupt
once, and using /Gs cleared it up.

good luck!
kevin dack
{known world}!ctvax!trsvax!kevin