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

2015-02-10 Thread ktietz at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=18649 Kai Tietz changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|---

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

2013-12-07 Thread ktietz at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18649 --- Comment #10 from Kai Tietz --- 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

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

2013-09-11 Thread ktietz at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18649 Kai Tietz changed: What|Removed |Added CC||ktietz at gcc dot gnu.org --- Comment #9 from

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

2012-01-11 Thread 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)

2012-01-11 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18649 Richard Guenther changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|

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

2011-11-05 Thread 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 --- Co

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

2005-08-11 Thread 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 r

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

2005-07-22 Thread 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.

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

2005-04-12 Thread 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

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

2005-04-08 Thread 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.cp

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

2004-12-05 Thread pinskia at gcc dot gnu dot org
-- What|Removed |Added Component|c++ |target http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18649