From: invalid AT erehwon DOT invalid (Graaagh the Mighty) Newsgroups: comp.os.msdos.djgpp Subject: Re: Peculiar behavior of program. Organization: Low Charisma Anonymous Message-ID: <3b2f09f2.4416801@news.primus.ca> References: <3b2efaa3 DOT 496489 AT news DOT primus DOT ca> <3B2F0771 DOT A2A1596A AT falconsoft DOT be> X-Newsreader: Forte Free Agent 1.11/32.235 Lines: 20 Date: Tue, 19 Jun 2001 08:16:30 GMT NNTP-Posting-Host: 207.176.153.40 X-Complaints-To: news AT primus DOT ca X-Trace: news1.tor.primus.ca 992920379 207.176.153.40 (Mon, 18 Jun 2001 23:12:59 EDT) NNTP-Posting-Date: Mon, 18 Jun 2001 23:12:59 EDT To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com On Tue, 19 Jun 2001 10:04:01 +0200, Tim Van Holder 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. 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, unless it invokes a kernel function or device driver that is buggy or doesn't enforce its preconditions. -- Bill Gates: "No computer will ever need more than 640K of RAM." -- 1980 "There's nobody getting rich writing software that I know of." -- 1980 "This antitrust thing will blow over." -- 1998 Combine neo, an underscore, and one thousand sixty-one to make my hotmail addy.