AIX: Perché il lancio di un'eccezione interrompe il codice multithread?

Question

Si interrompe quando viene generata un'eccezione C ++ durante l'esecuzione del codice compilato con -pthread.

Piattaforma: AIX 5.3 livello tecnico 8 Compilatore: gcc 3.4.6 Linker: linker AIX 1.65.2.4

Codice test:

// exception.cpp
#include <iostream>

class MyException
{
public:
        MyException(){}
        virtual ~MyException(){};
};

void gTest()
{
        throw MyException();
}

int main()
{
        try
        {
                gTest();
        }
        catch(MyException const & ex)
        {
                std::cout << "exception was caught" << std::endl;
        }

        return 0;
}


$ g++ exception.cpp
$ ./a.out
exception was caught
$ g++ -pthread exception.cpp
$ ./a.out
terminate called after throwing an instance of 'MyException'
IOT/Abort trap (core dumped)
$ gdb a.out
GNU gdb 6.0
Copyright 2003 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 "powerpc-ibm-aix5.1.0.0"...
(gdb) run
Starting program: /home/leeder/except/a.out
terminate called after throwing an instance of 'MyException'

Program received signal SIGABRT, Aborted.
Switching to Thread 1
0xd0124834 in pthread_kill () from /usr/lib/libpthreads.a(shr_xpg5.o)
(gdb) bt
#0 0xd0124834 in pthread_kill () from /usr/lib/libpthreads.a(shr_xpg5.o)
#1 0xd01242a8 in _p_raise () from /usr/lib/libpthreads.a(shr_xpg5.o)
#2 0xd0359bdc in raise () from /usr/lib/libc.a(shr.o)
#3 0xd03b7efc in abort () from /usr/lib/libc.a(shr.o)
#4 0xd0ca1800 in __gnu_cxx::__verbose_terminate_handler() () at ../../.././libstdc++-v3/libsupc++/vterminate.cc:96
#5 0xd0ca1220 in __cxxabiv1::__terminate(void (*)()) (handler=0)
at ../../.././libstdc++-v3/libsupc++/eh_terminate.cc:43
#6 0xd0ca128c in std::terminate() () at ../../.././libstdc++-v3/libsupc++/eh_terminate.cc:53
#7 0xd0ca7cfc in __cxa_throw (obj=0x200084e8, tinfo=0xffffffff, dest=Cannot access memory at address 0xffffffff
)
at ../../.././libstdc++-v3/libsupc++/eh_throw.cc:80
#8 0x100008dc in gTest() ()
#9 0x100009f0 in main ()
(gdb)

Qualcuno ha visto qualcosa di simile?

Pensi che l'aggiornamento a gcc 4 sarebbe di aiuto?

Che dire del passaggio al compilatore xl di IBM?

Grazie.

Answer 1

g ++ 4.3.2 sembra funzionare bene per questo problema. Anche xlC v10 funziona.

Answer 2

Ho provato il tuo programma su AIX:

  

oslevel -r

     

5200-08

con g ++ --version

  

g ++ (GCC) 3.3.2

     

g ++ -o ex -pthread ex.cpp

comporterà simboli non trovati in fase di esecuzione (pthread_mutex_t)

Tuttavia, se lo costruisci come:

  

g ++ -o ex -lpthread ex.cpp

funziona perfettamente con gli effetti previsti. Immagino che questo potrebbe essere un problema di collegamento con le librerie pthread giuste.