mysql-workbench-6.0.8 fails to connect to a mysql database instance with message libgcc_s.so.1 must be installed for pthread_cancel to work The reported library is not missing: > locate libgcc_s.so.1 /usr/lib64/debug/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/libgcc_s.so.1.debug /usr/lib64/debug/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/32/libgcc_s.so.1.debug /usr/lib64/debug/usr/lib/gcc/x86_64-pc-linux-gnu/4.8.2/libgcc_s.so.1.debug /usr/lib64/debug/usr/lib/gcc/x86_64-pc-linux-gnu/4.8.2/32/libgcc_s.so.1.debug /usr/lib64/gcc/x86_64-pc-linux-gnu/4.7.3/libgcc_s.so.1 /usr/lib64/gcc/x86_64-pc-linux-gnu/4.7.3/32/libgcc_s.so.1 /usr/lib64/gcc/x86_64-pc-linux-gnu/4.8.2/libgcc_s.so.1 /usr/lib64/gcc/x86_64-pc-linux-gnu/4.8.2/32/libgcc_s.so.1 > file usr/lib64/gcc/x86_64-pc-linux-gnu/4.8.2/libgcc_s.so.1 file /usr/lib64/gcc/x86_64-pc-linux-gnu/4.8.2/libgcc_s.so.1 /usr/lib64/gcc/x86_64-pc-linux-gnu/4.8.2/libgcc_s.so.1: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, stripped >ldconfig -p |grep libgcc_s.so libgcc_s.so.1 (libc6,x86-64) => /usr/lib/gcc/x86_64-pc-linux-gnu/4.8.2/libgcc_s.so.1 libgcc_s.so.1 (libc6,x86-64) => /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/libgcc_s.so.1 libgcc_s.so.1 (libc6) => /usr/lib/gcc/x86_64-pc-linux-gnu/4.8.2/32/libgcc_s.so.1 libgcc_s.so.1 (libc6) => /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/32/libgcc_s.so.1 libgcc_s.so (libc6,x86-64) => /usr/lib/gcc/x86_64-pc-linux-gnu/4.8.2/libgcc_s.so libgcc_s.so (libc6,x86-64) => /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/libgcc_s.so libgcc_s.so (libc6) => /usr/lib/gcc/x86_64-pc-linux-gnu/4.8.2/32/libgcc_s.so libgcc_s.so (libc6) => /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/32/libgcc_s.so > source /usr/bin/mysql-workbench gdb /usr/bin/mysql-workbench-bin output: attached. emerge --info: attached As per discussions in http://bugs.mysql.com/bug.php?id=42850, if nptl_pthread_exit_hack_handler function (in my_thr_init.c) is modified and pthread_exit(0) is commented out, then mysql-workbench can be used to connect to a database without error. The mysql-workbench GUI would still have an issue at exit: if an attempt to connect to a database fails, the the GUI can not be closed gracefully. Reproducible: Always Steps to Reproduce: 1.Launch mysql-workbench 2.Go to Database -> Connect to database (top menu) 3.Create a connection a MySql database (hostname, username); storing the connection is optional 4. click OK 5. try to use the connection created in previous step Actual Results: mysql-workbench-bin exits: Program received signal SIGABRT, Aborted last message on the console: libgcc_s.so.1 must be installed for pthread_cancel to work
Created attachment 368932 [details] emerge --info
Created attachment 368934 [details] gdb mysql-workbench-bin
Did you try re-emerging dev-db/mysql-workbench? You may have switched to a newer libgcc_s.so when you upgraded your system compiler (gcc-config -l).
(In reply to Jeroen Roovers from comment #3) Yes, re-emerged after checking gcc-config output: > gcc-config -l [1] x86_64-pc-linux-gnu-4.7.3 [2] x86_64-pc-linux-gnu-4.8.2 * Still no difference after re-emerging.
I can't reproduce this issue, and the bug you reference has been closed a long time ago. I'm not sure what to do about this. If this also happens when you build mysql-workbench by hand then it might be best to report this upstream directly.
I had the problem too on my 32 and 64 bits machines. What I did to resolve it is remove the "strip-flags" line and emerge it agaibn with LDFLAGS=-lgcc_s So something seems wrong in my (our?) LDFLAGS from emerge --info: LDFLAGS="-Wl,-O1 -Wl,--as-needed -Wl,-z,now" "-Wl,-z,now" maybe
I have just tested building mysql-workbench 6.3.4 with -Wl,-z,now and (after fixing a different bug) this now works as expected for me. Could you retest with this version and reopen the bug if the issue is still there?