From: Chris Frolik Newsgroups: comp.os.msdos.djgpp Subject: gcc crash Date: Mon, 13 Apr 1998 23:37:27 -0500 Organization: IndyNet - Indys Internet Gateway (info AT indy DOT net) Lines: 38 Message-ID: <3532E807.18DC@indy.net> NNTP-Posting-Host: ip72-53.ts.indy.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk Hello, I was compiling with djgpp today, and gcc decided to crash...here's the traceback: C:\Chris\C\xapheus>make -f makefile.txt gcc -c -g -O3 -finline -Wimplicit -Wreturn-type -Werror -m486 newplyr.c Exiting due to signal SIGTRAP Debug at eip=0009172d eax=004bc284 ebx=00000007 ecx=004bcfe8 edx=000002a0 esi=0000001f edi=00000007 ebp=001d9c28 esp=001d9c10 program=d:/djgpp/bin\cc1.exe cs: sel=015f base=831d0000 limit=004bffff ds: sel=0167 base=831d0000 limit=004bffff es: sel=0167 base=831d0000 limit=004bffff fs: sel=013f base=00026170 limit=0000ffff gs: sel=0177 base=00000000 limit=ffffffff ss: sel=0167 base=831d0000 limit=004bffff Call frame traceback EIPs: 0x0009172d 0x00027c91 0x00016d9d 0x00007a6f 0x00026d32 0x000290e2 0x000efd9a make.exe: *** [newplyr.o] Error 1 I know my djgpp installation isn't broken...I've used it for a long time with no problems like this. I noticed the "debug at" statement up there...and SIGTRAP seems to have something to do with debuggers too. How do I avoid this crash? Thanks, --Chris Frolik frolikcc AT indy DOT net