Informix - Problembeschreibung
Problem IT28360 | Status: Geschlossen |
SEGV IN IFX_TH_MUTEX_LOCK WHEN COMPILING WITH "-THREAD" | |
Produkt: | |
IBM CSDK / 5724C2381 / 410 - CSDK 4.10 | |
Problembeschreibung: | |
sing "-thread" in a simple ESQL/C code fails with a segv in: $ esql t.ec -thread $ gdb ./a.out GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1 ... Program received signal SIGSEGV, Segmentation fault. __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67 67 ../nptl/pthread_mutex_lock.c: No such file or directory. (gdb) where #0 __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67 #1 0x00007ffff74c38c8 in ifx_th_mutex_lock () from /data/informix/IBM/12.10/lib/esql/libthos.so #2 0x00007ffff74c336c in ifxOS_th_mutex_lock () from /data/informix/IBM/12.10/lib/esql/libthos.so #3 0x00007ffff74c3464 in ifxOS_thread_mutexLock () from /data/informix/IBM/12.10/lib/esql/libthos.so #4 0x00007ffff7b9209b in asf_init () from /data/informix/IBM/12.10/lib/esql/libthsql.so #5 0x00007ffff7b950ea in sqli_connect_open_tcb () from /data/informix/IBM/12.10/lib/esql/libthsql.so #6 0x00007ffff7b9596e in sqli_connect_open () from /data/informix/IBM/12.10/lib/esql/libthsql.so #7 0x0000000000400940 in db_init () #8 0x00000000004009c4 in main () | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Users of CSDK prior to 4.10.xC13. * **************************************************************** * PROBLEM DESCRIPTION: * * Segmentation Violation in ifx_th_mutext_lock when compiling * * with "-thread" option. * **************************************************************** * RECOMMENDATION: * **************************************************************** | |
Local-Fix: | |
Lösung | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 07.03.2019 24.09.2019 24.09.2019 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
4.10.xC13 | |
Problem behoben lt. FixList in der Version |