Path: utzoo!utgpu!water!watmath!clyde!rutgers!rochester!PT.CS.CMU.EDU!cadre!pitt!darth!apex!gary
From: gary@apex.UUCP (Gary Wisniewski)
Newsgroups: comp.lang.c
Subject: Re: How to Trap Runtime System Error under MSC?
Summary: You already have the source code!
Message-ID: <317@apex.UUCP>
Date: 28 Jan 88 04:42:25 GMT
References: <11279@brl-adm.ARPA> <1854@optilink.UUCP>
Reply-To: gary@apex.UUCP (Gary Wisniewski)
Organization: Apex Software Corp., Pittsburgh, Pa.
Lines: 26

In article <1854@optilink.UUCP> cramer@optilink.UUCP (Clayton Cramer) writes:
>> Michael Harris asks,
>> 
>> >Can anyone tell me how to trap Microsoft C "serious runtime errors", e.g.,
>> >"Error 2000 Stack Overflow", before they print to the terminal screen?
>> 
>
>You might find out if the $150 Microsoft charges for runtime library
>routine sources includes __chkstk.  If not, take a look at the disassembled
>code from CodeView -- it's tiny.
>
>Clayton E. Cramer

The MSC Startup Code diskette contains source to both the __chkstk routine
(in the chkstk.asm module) and to the error message generator.  You can
modify these and rebuild the startup code (CRT0.OBJ et.al.).  We rewrote
it all to take advantage of EMS, etc.

BY THE WAY!  The MSC runtime source code DOES not include floating point
and compiler "glue" modules like $i8_foo_bar you may have seen in the
maps or while debugging ... just the documented stuff is included ...
we were depressed when ours arrived.

-- 
Gary J. Wisniewski				Apex Software Corporation
{allegra,bellcore,cadre}!pitt!darth!apex!gary	Phone: (412) 681-4343