I have faced with a problem when I was porting an application from gcc 3.4.4
to gcc 4.3.1 on HP-UX 11.23 PA RISC. Here is the backrtace. By the way the
same application compiled with gcc 4.3.1 works perfectly on HP-UX 11.31. As
you can see the problem happens when a thread is about to finish and calling
pthread_exit(). I searched for a possible solution and found that there were
complains as to this functions in gcc 4.3.0, but actually they were not
related to emutls_destroy(). Also I have to mention that gcc was downloaded
from the HP-UX site and was said to be adopted for HP-UX.
(gdb) bt
#0 0xc0000000002013a4 in kill+0x2c () from /lib/pa20_64/libc.2
#1 0xc0000000001accfc in raise+0x2c () from /lib/pa20_64/libc.2
#2 0xc0000000001e6d30 in abort_C+0x180 () from /lib/pa20_64/libc.2
#3 0xc0000000001e6d94 in abort+0x1c () from /lib/pa20_64/libc.2
#4 0x400000000044228c in
_ZN5os_sp11app_env_log15sigsegv_handlerEiP9__siginfoPv ()
at ../../../src/common/rating_shared/app_env_log.cpp:264
#5 <signal handler called>
#6 0xc0000000001a1074 in free+0x29c () from /lib/pa20_64/libc.2
#7 0xc000000000ba5ed8 in emutls_destroy () at
/tmp/gcc-4.3.1.tar.gz/gcc-4.3.1/libgcc/../gcc/emutls.c:73
#8 0xc00000000008dd98 in __specific_data_thread_exit+0x318 () from
/lib/pa20_64/libpthread.1
#9 0xc000000000097a6c in pthread_exit+0x62c () from
/lib/pa20_64/libpthread.1 #10 0xc0000000000949f0 in
__pthread_bound_body+0xe0 () from /lib/pa20_64/libpthread.1
#11 0xc0000000000c451c in __pthread_bound_start+0x14 () from
/lib/pa20_64/libpthread.1
(gdb)
--
View this message in context: http://www.nabble.com/Possibly-emutls_destroy%28%29-has-a-problem-on-HP-UX-11%2C23-PA-RISC-tp19943843p19943843.html
Sent from the gcc - Help mailing list archive at Nabble.com.
