Xref: utzoo comp.windows.ms.programmer:3026 comp.lang.pascal:7097
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!wuarchive!uunet!microsoft!bobsc
From: bobsc@microsoft.UUCP (Bob SCHMIDT)
Newsgroups: comp.windows.ms.programmer,comp.lang.pascal
Subject: Re: Question on UAE's when running TPW
Message-ID: <72835@microsoft.UUCP>
Date: 10 Jun 91 03:22:32 GMT
References: <91157.094647F0O@psuvm.psu.edu>
Reply-To: bobsc@microsoft.UUCP (Bob SCHMIDT)
Organization: Microsoft Corp., Redmond WA
Lines: 34

In article <91157.094647F0O@psuvm.psu.edu> F0O@psuvm.psu.edu writes:
%% 
%%    Since when doing program development in TPW, one is likely to get
%% many UAE's(especially when you're first starting out) :-)
%% I was wondering if your other programs are protected from
%% these errors or not.  I wouldn't like to have to exit windows and restart
%% every time I would encounter a UAE, but maybe this is the best way to
%% work?
%%    I've heard other people say when you're running other windows programs
%% and get a UAE, you should exit ASAP to avoid any possible further damage.
%% 
%%                                                            [Tim]

All Windows apps run in the same address space (using the same LDT).
I see apps trounce one another all the time.  The safest thing, of course,
is to *reboot* between UAEs.  That's a little draconian; even just
re-running Windows is a pain.

I suggest that the remedy depends on where the UAE occurred.
If you die in your own code, then you are often safe just exiting
your app and restarting.  However, if you UAE deep in the bowels of
Windows (e.g., while calling a Windows API), then you may have confused
Windows enough that you should exit and rerun.

As much of a hassle as it is, until you get some experience ferretting
out UAEs, the conservative course is probably best.  If/when
Windows goes to multiple LDTs (a la OS/2), life will become much
more predictable.

--
--  Bob Schmidt        bobsc@microsoft.UUCP
--
--  Bellevue WA USA    Windows SDK Support
--  Sydney NSW AUS     Developer Support (after 1 Oct)