Date: Tue, 24 Oct 2000 10:48:59 -0700 (PDT) From: lampa@fee.vutbr.cz To: freebsd-gnats-submit@FreeBSD.org Subject: gnu/22274: /usr/lib/libgcc.a is not thread safe Message-ID: <20001024174859.E45CA37B479@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 22274 >Category: gnu >Synopsis: /usr/lib/libgcc.a is not thread safe >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Oct 24 10:50:00 PDT 2000 >Closed-Date: >Last-Modified: >Originator: Petr Lampa >Release: 4.1.1 >Organization: Brno University of Technology, CSE dept. >Environment: FreeBSD boco.fee.vutbr.cz 4.1.1-STABLE FreeBSD 4.1.1-STABLE >Description: Installed gcc library /usr/lib/libgcc.a is not compiled using --enable-threads. The description of this configure argument in gcc-2.95.2 is wrong, it should be on not only for Objective C, but also for C++ to enable thread safe stack unwinding during exception processing. From Orbacus C++ JTC-1.0.13 (www.ooc.com): IMPORTANT: You must ensure that the version of gcc that you are using was configured with --enable-threads. Without this exception handling is not thread safe. To determine if this is the case, run nm on libgcc.a and verify that pthread symbols are present. >How-To-Repeat: In my case regular arithmetic exception resulted in segmentation fault. If the program was linked with the proper library, exception is correctly catched and reported. >Fix: Ship /usr/lib/libgcc.a compiled with --enable-threads! >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001024174859.E45CA37B479>