delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2001/06/19/11:00:13

From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Peculiar behavior of program.
Date: 19 Jun 2001 14:48:49 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 32
Message-ID: <9gnooh$9pv$1@nets3.rz.RWTH-Aachen.DE>
References: <3b2efaa3 DOT 496489 AT news DOT primus DOT ca> <3B2F0771 DOT A2A1596A AT falconsoft DOT be> <3b2f09f2 DOT 4416801 AT news DOT primus DOT ca>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 992962129 10047 137.226.32.75 (19 Jun 2001 14:48:49 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 19 Jun 2001 14:48:49 GMT
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Graaagh the Mighty <invalid AT erehwon DOT invalid> wrote:
> On Tue, 19 Jun 2001 10:04:01 +0200, Tim Van Holder
> <tim DOT vanholder AT falconsoft DOT be> sat on a tribble, which squeaked:

>>This is all very interesting, but it would be a LOT more informative
>>and helpful if you posted the code that resulted in the broken
>>behaviour.

> It's about a thousand lines long and the bug is *very* unstable --
> almost any change whatsoever stops it reproducing.

A wild pointer, almost certainly. Such "Heisenbugs" are typical of
accessing uninitialized memory, esp. for writing through a pointer
that wasn't properly initialized to point to somewhere sensible,
before. Each time you recompile or even re-run the program, the bug
may toggle into and out of existance.

> I won't have a problem once I can get a decent traceback. Why is it
> not generating the "call frame traceback EIPs"? And why does it crash
> Windows? A protected mode task should be utterly unable to bring the
> OS down, 

"Should": yes. But reality shows that "should" rules are far too
seldomly paid any respect.  And 9x is a rather prominent example of
that, regrettably.

Protected mode means that the CPU offers hardware assistance that an
OS can use to enforce proper segregation between independant tasks.
But by no means does that imply that the OS *has* to do that.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019