X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-bounces using -f From: Hans-Bernhard Broeker Newsgroups: comp.os.msdos.djgpp Subject: Re: More Info Date: 29 Jan 2002 13:39:10 GMT Organization: Aachen University of Technology (RWTH) Lines: 28 Message-ID: References: <3C561045 DOT 42E04404 AT xtra DOT co DOT nz> <3c561138 DOT sandmann AT clio DOT rice DOT edu> <3C563CFF DOT AF5763D6 AT xtra DOT co DOT nz> NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de X-Trace: nets3.rz.RWTH-Aachen.DE 1012311550 11125 137.226.32.75 (29 Jan 2002 13:39:10 GMT) X-Complaints-To: abuse AT rwth-aachen DOT de NNTP-Posting-Date: 29 Jan 2002 13:39:10 GMT Originator: broeker@ To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Greg & Steph wrote: > Hi again, > Go32-v2 runs ok, DPMI mem available 13457Kb, DPMI swap space > available 47235Kb. Dos ver 6.22. Looks sane > Config.sys... > Autoexec.bat... Both look sane. > Typing "rhide" results in... > General Protection Fault at eip=233; flags=3206 [...] > "gcc hello.c -o hello.exe" results in... > Exiting due to signal SIGSEGV > General Protection Fault at eip=00000237 eax=00000018 One rather suspicious detail is that the eip of the crashing instruction is almost the same in both cases. As you're using DOS, this might even be the exact same byte of RAM chip holding the failing instruction. That suggests you may well have a hardware instability problem, quite probably bad RAMs. Go check your memory chips, or any other hardware you added to that machine recently. -- Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) Even if all the snow were burnt, ashes would remain.