From: "Andrew Crabtree" <andrewc AT rosemail DOT rose DOT hp DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Bugs in 2.8.0?
Date: Wed, 11 Mar 1998 09:14:23 -0800
Organization: Hewlett Packard
Lines: 27
Message-ID: <6e6gph$66e$1@rosenews.rose.hp.com>
References: <m0yCie4-000S2iC AT inti DOT gov DOT ar>
NNTP-Posting-Host: ros51675cra.rose.hp.com
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk


Salvador Eduardo Tropea (SET) wrote in message ...
Jerzy Witkowski <Jerzy DOT Witkowski AT ii DOT uni DOT wroc DOT pl> wrote:
>> Second, rather serious: exceptions cannot be caught.  The
>> following program:
>that the fact is the reverse: Now in 2.8.0 exceptions works like the C++
>standard says and hence some specific switch (like the RTTI switch) are
enabled
>by default. Please read the news from 2.8.0 and the 2.8.0 manuals.
I still haven't downloaded 2.8.0 but I suspect that he is correct in stating
that exception handling
doesn't work properly.  I sent message to the workers list asking someone to
verify before the 2.8 release but I guess that nobody did.  After pgcc 1.0.1
release I had the same problem reported.  It appears that in order for
exception handling to work (as it is defaulted), you must replace ld.exe
with collect2.  If you don't do that then the exception tables don't get
built properly.  I have been working at porting collect2 over from egcs but
it is very difficult, it uses many posix features that djgpp doesn't have.
A possible solution is
to enable sjlj exceptions.  The default gcc uses is -fexceptions, try
manually specifying -fsjlj-exceptions
on the compile line and see if that works.

HTH

Andy