X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f From: "Mike C" Newsgroups: comp.os.msdos.djgpp Subject: Grevious RHIDE fault Lines: 47 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Message-ID: Date: Sun, 19 Feb 2006 19:00:57 GMT NNTP-Posting-Host: 86.13.155.138 X-Complaints-To: http://www.ntlworld.com/netreport X-Trace: newsfe7-win.ntli.net 1140375657 86.13.155.138 (Sun, 19 Feb 2006 19:00:57 GMT) NNTP-Posting-Date: Sun, 19 Feb 2006 19:00:57 GMT Organization: ntl Cablemodem News Service To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Folks, I have a real nasty in my DGJPP programming environment. I work on a Windows 2000 laptop About a month ago, while I was programming, I pressed F7 on RHIDE to compile and go to the first instruction - and it said "Exiting due to signal SIGSEGV" and wrote a whole lot of register stuff on my screen. RHIDE was still up. When I killed the DOS window, restarted it and restarted RHIDE, it immediately showed the same thing. When I checked my files, my C source file had been overwritten with this register stuff and I had lost a lot of work. It has just happened again. I have been working on this program all day, and all I have to show for it is (this is the actual content of my C-source file).... Exiting due to signal SIGSEGV General Protection Fault at eip=001afe60 eax=ff9b0000 ebx=ff9b0000 ecx=000001cc edx=ff9c0000 esi=00004000 edi=ff9b4010 ebp=002edaec esp=002edab4 program=d:\djgpp\Files\Serial\slave.exe cs: sel=01a7 base=01cc0000 limit=7e32ffff ds: sel=01af base=01cc0000 limit=7e32ffff es: sel=01af base=01cc0000 limit=7e32ffff fs: sel=01bf base=00000000 limit=0010ffff gs: sel=01bf base=00000000 limit=0010ffff ss: sel=01af base=01cc0000 limit=7e32ffff App stack: [00097a14..00017a14] Exceptn stack: [00017974..00015a34] Quite frequently if I am single-stepping a program, it suddenly quits out to the DOS screen. If I restart RHIDE, everything is OK again, though it's a bit of a nuicance. Could this be related? I'd certainly appreciate some help here. I certainly don't want this to happen too often! This has just cost me six or seven hours. When a program fails, but can be restarted, it's a bother, but when it writes on top of your work, that's a P.I.T.A! Thanks, Mike.