[Bug target/18649] terminate called after throwing - IOT/Abort trap (core dumped)

[Bug target/18649] terminate called after throwing - IOT/Abort trap (core dumped)

[bucreev_1 at mail dot ru]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18649

bucreev_1 at mail dot ru changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bucreev_1 at mail dot ru

--- Comment #6 from bucreev_1 at mail dot ru 2011-11-05 09:21:35 UTC ---
This example (Allen Skees 2004-11-24 15:48:41 UTC) also does not work correctly
when using gcc version 4.5.2.

D:\MinGW\bin>gcc -v
Using built-in specs.
COLLECT_GCC=D:\MinGW\bin\gcc.EXE
COLLECT_LTO_WRAPPER=d:/mingw/bin/../libexec/gcc/mingw32/4.5.2/lto-wrapper.exe
Target: mingw32
Configured with: ../gcc-4.5.2/configure
--enable-languages=c,c++,ada,fortran,obj
c,obj-c++ --disable-sjlj-exceptions --with-dwarf2 --enable-shared
--enable-libgo
mp --disable-win32-registry --enable-libstdcxx-debug
--enable-version-specific-r
untime-libs --disable-werror --build=mingw32 --prefix=/mingw
Thread model: win32
gcc version 4.5.2 (GCC)

[Bug target/18649] terminate called after throwing - IOT/Abort trap (core dumped)

[rguenth at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18649

Richard Guenther <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2012-01-11
                 CC|                            |dje at gcc dot gnu.org
     Ever Confirmed|0                           |1

--- Comment #7 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-01-11 12:43:52 UTC ---
Still an issue?

[Bug target/18649] terminate called after throwing - IOT/Abort trap (core dumped)

[bucreev_1 at mail dot ru]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18649

--- Comment #8 from bucreev_1 at mail dot ru 2012-01-11 15:26:45 UTC ---
There are no questions. Just to inform you that in version of gcc 4.5.2. this
example does not work.

[Bug target/18649] terminate called after throwing - IOT/Abort trap (core dumped)

[ktietz at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18649

Kai Tietz <ktietz at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ktietz at gcc dot gnu.org

--- Comment #9 from Kai Tietz <ktietz at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #7)
> Still an issue?

gcc 4.8 and upward still have this issue.

[Bug target/18649] terminate called after throwing - IOT/Abort trap (core dumped)

[ktietz at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18649

--- Comment #10 from Kai Tietz <ktietz at gcc dot gnu.org> ---
For mingw-code this bug is fixed.  It was caused by a bug in SjLj catch-reason.
 Issue is fixed for 32-bit and 64-bit mingw targets for all open branches.
As report was for different targets, it would be good if PPC maintainer could
verify that this issue is fixed for this target, too.

[Bug target/18649] terminate called after throwing - IOT/Abort trap (core dumped)

[ktietz at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=18649

Kai Tietz <ktietz at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |RESOLVED
         Resolution|---                         |WORKSFORME

--- Comment #11 from Kai Tietz <ktietz at gcc dot gnu.org> ---
So waited long enough for a reply of PPC maintainer.  I assume it is fixed too.

[Bug target/18649] terminate called after throwing - IOT/Abort trap (core dumped)

[jkj at sco dot com]

------- Additional Comments From jkj at sco dot com  2005-08-11 09:18 -------
On UnixWare I have a very similar failure. It seems to be -fPIC that's wreaking
the havoc. I have an almost identical test case, and it aborts with:
terminate called after throwing an instance of 'int'
terminate called recursively

This only happens when compiling a2.cpp with -fPIC and producing a .so. If you
link the two together, it works fine. This was with 3.4.4.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18649

[Bug target/18649] terminate called after throwing - IOT/Abort trap (core dumped)

[pinskia at gcc dot gnu dot org]

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
   GCC host triplet|powerpc-ibm-aix5.1.0.0      |
 GCC target triplet|                            |powerpc-ibm-aix5.1.0.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18649

[Bug target/18649] terminate called after throwing - IOT/Abort trap (core dumped)

[cmchugh at callixa dot com]

------- Additional Comments From cmchugh at callixa dot com  2005-04-13 00:41 -------

If I compile and link the example in my last comment (shown below) with
-pthread, it will always run. If I don't it will always core dump. This is with
g++ 3.4.3 on AIX 5.2. Does anyone know if the same program compiled with g++
3.3.3 will behave the same way on AIX 5.2 ? (i.e. run okay when compiled and
linked with -pthread but abort otherwise ?)

bluetrance:13391$ cat a2.cpp
void mycall()
{
        throw 0;
}
bluetrance:13391$ cat a1.cpp
                                                                                 
extern void mycall();
 
int main()
{
        try {
                mycall();
        } catch (int i) {
                return i;
        }
        return 1;
}
 
 
bluetrance:13391$ g++ -fPIC -DPIC -shared -pthread -o liba2.a a2.cpp
bluetrance:13391$ g++ -fPIC -DPIC -o a1 a1.cpp -pthread -L. -la2

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18649

[Bug target/18649] terminate called after throwing - IOT/Abort trap (core dumped)

[cmchugh at callixa dot com]

------- Additional Comments From cmchugh at callixa dot com  2005-04-08 20:18 -------
I downloaded and built 3.4.3 on AIX 5.2, and this bug does still exist; I tried
the following program (scarfed from 13391) and it crashes every time. Is there
any resolution/fix ? 


bluetrance:13391$ more a2.cpp
void mycall()
{
        throw 0;
}
bluetrance:13391$ more a1.cpp
                                                                                 
extern void mycall();
 
int main()
{
        try {
                mycall();
        } catch (int i) {
                return i;
        }
        return 1;
}
 
 
bluetrance:13391$ g++ -fPIC -DPIC -shared -o liba2.a a2.cpp
bluetrance:13391$ g++ -fPIC -DPIC -o a1 a1.cpp -L. -la2
bluetrance:13391$ a1
terminate called after throwing an instance of 'i'
IOT/Abort trap (core dumped)

bluetrance:build$ g++ --v
Reading specs from /usr/local/bin/../lib/gcc/powerpc-ibm-aix5.2.0.0/3.4.3/specs
Configured with: /export/xtegra3/gcc-3.4.3/gcc-3.4.3/configure
--enable-languages=c,c++ --enable-threads=aix --disable-nls
--prefix=/export/xtegra3/gcc-3.4.3/installdir
Thread model: aix
gcc version 3.4.3

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18649

[Bug target/18649] terminate called after throwing - IOT/Abort trap (core dumped)

[pinskia at gcc dot gnu dot org]

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|c++                         |target


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18649