Xref:	news-dnh.mv.net comp.os.msdos.djgpp:1050
Path:	news-dnh.mv.net!mv!news.sprintlink.net!simtel!lll-winken.llnl.gov!enews.sgi.com!decwrl!waikato!comp.vuw.ac.nz!tao.sans.vuw.ac.nz!empty
From:	empty AT sans DOT vuw DOT ac DOT nz (Malcolm Taylor)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Strange crashes in g++
Date:	21 Jul 1995 08:40:07 GMT
Organization:	SANS, Student Access Network System
Lines:	15
References:	<iXDk9c1w200w AT alcyone DOT darkside DOT com>
Nntp-Posting-Host:	tao.sans.vuw.ac.nz
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway:	from newsgroup comp.os.msdos.djgpp

Erik Max Francis (max AT alcyone DOT darkside DOT com) wrote:
: If I'm compiling a C++ program with gcc (in DJGPP 1.12), and if I'm 
: getting a lot of errors, oftentimes I'll see a crash within g++.  When 
: the crash occurs (if it does), it usually appears to be a segmentation 
: fault.

The compiler was written not expecting unknown symbols, obviously when it 
comes across a symbol that isn't in one of it's tables it comes up with 
an access to memory that is outside the table, hence the segmentation 
fault. It isn't a crash as such, just caused by the compiler looking for 
info about a symbol where there is none.
I have no idea whether it would be possible to remove these, or whether 
it is worth doing.

Malcolm

- Raw text -