Re: C++ Exception Handling Bug

["Andris Pavenis" <pavenis at lanet dot lv>]

On Dec  3, 1998, Mark-Andre Hopf <hopf@informatik.uni-rostock.de> wrote:
> 
> >  I ran into bug in the C++ exception handling code generated by egcs-1.1.x:
> 
> I can't reproduce this problem with egcs 1.1.1 on RedHat Linux 5.1.
> Are you sure it's not a shared library problem, such as linking the
> wrong shared library?  gdb should help you find that out, or could at
> least get us a stack trace.
> 

Tried egcs-1.1.1-release  (DJGPP, target=i586-pc-msdosdjgpp). Without optimizations
(g++ -x c++ foo.ii -o xxx.exe) there is no crash.
With optimizations (I tested -O1, -O2, -O3) I'm
geting SIGABRT.

Otherwise seems that previous exceptions problems
with DJGPP are gone (except when -fomit-frame-pointer is being used, then exceptions are still partially broken)

C:\DJGPP\DOC\Bugs\Exceptions>gdb xxx.exe
GNU gdb 4.17
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-pc-msdosdjgpp"...
(gdb) b abort
Breakpoint 1 at 0x4d5b
(gdb) r
Starting program: c:/djgpp/doc/Bugs/Exceptions/xxx.exe

Breakpoint 1, 0x4d5b in abort ()
(gdb) where
#0  0x4d5b in abort ()
#1  0x2745 in copy_reg (reg=16, udata=0x8fcd4, target_udata=0x8fbf4)
#2  0x2a48 in __throw ()
#3  0x1623 in foo::f2 (this=0x8fd7f) at 981204.ii:27
#4  0x1570 in main (argc=1, argv=0x903a4) at 981204.ii:13
#5  0x4962 in __crt1_startup ()
(gdb)


-----
See the original message at http://www.egroups.com/list/egcs-bugs/?start=8651