TMG-L Archives

Archiver > TMG > 2002-03 > 1015190805


From: Richard Brogger <>
Subject: Re: [TMG] Memory in Win 98 SE, Win ME,Win XP/XP Pro (was: Exhibit log)
Date: Sun, 03 Mar 2002 15:26:45 -0600
References: <5.1.0.14.0.20020302183300.00acca80@mail.fscv.net><OE135uKxeSuPcw3LyyU00005116@hotmail.com><5.1.0.14.0.20020302233030.0270f8f0@mail.fscv.net><000501c1c2d8$d14159d0$60440142@master>


Cliff Soderback wrote:
>
> snip
>
> When programs crash(stop responding) 99.999% of the time it is
> that there is an error in the program's code.
>
Hi Cliff,

Is the error almost always in the code of the program that crashes? Or
can a poorly written program cause other programs to crash?

I rarely have problems with Word locking up but it did so four times
yesterday when I had two other programs open at the same time. Since
it was Word that locked up, should I assume the error was in Word or
could the error be in one of the other program's code and interfering
with Word?

When two programs try to write to the same address in memory, one of
them is wrong but how do I know which one? I figure it could happen
two ways. Program A wrote to the address it had reserved but program B
tried to use the same address. Thus program B is in error. Program A
wrote to an address reserved by B and when B tried to write to that
address, it crashed. Thus program A is in error.

In either scenario the second program maybe should have had code to
trap the error. If I were a programmer and following the rules, am I
at fault if another program does not follow those rules? Is a
programmer supposed to have enough foresight to plan for every
possible way the rules might be violated by someone else? From what
little I know of writing code, it is hard enough to get it right
without planning for every possible mistake someone else might make in
their code.

Richard Brogger

This thread: