Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stdcxx-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: local policy)
Mime-Version: 1.0
Date: Tue, 26 Jun 2007 06:05:57 -0800
Message-ID: <5CF326C9D2E.0000016Bmbrown@inbox.com>
From: Mark Brown <mbrown@inbox.com>
Subject: RE: status of thread safety tests
To: stdcxx-dev@incubator.apache.org
In-Reply-To: <46774B7B.8070105@roguewave.com>
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

22.locale.num.put.mt gets a SIGSEGV on my system (Fedora 6) even with a =
single thread. Here's the output of gdb:

=24 gdb ./22.locale.num.put.mt
GNU gdb Red Hat Linux (6.5-15.fc6rh)
Copyright (C) 2006 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 =22show copying=22 to see the conditions.
There is absolutely no warranty for GDB.  Type =22show warranty=22 for =
details.
This GDB was configured as =22x86_64-redhat-linux-gnu=22...
(no debugging symbols found)
Using host libthread_db library =22/lib64/libthread_db.so.1=22.

(gdb) run --nthreads=3D1
Starting program: =
/home/mbrown/stdcxx-gcc-4.1.1-12D/tests/22.locale.num.put.mt -
-nthreads=3D1
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
=5BThread debugging using libthread_db enabled=5D
=5BNew Thread 46912499232352 (LWP 32189)=5D
(no debugging symbols found)
=23 INFO (S1) (10 lines):
=23 TEXT:=20
=23 COMPILER: gcc 4.1.1, __VERSION__ =3D =224.1.1 20070105 (Red Hat =
4.1.1-51)=22
=23 ENVIRONMENT: amd64/LP64 running linux-elf (unknown release) with glibc =
2.5
=23 FILE: 22.locale.num.put.mt.cpp
=23 COMPILED: Jun 26 2007, 07:52:50
=23 COMMENT: thread safety
=23=23=23=23=23=23=23=23=23=23=23=23=23=23=23=23=23=23=23=23=23=23=23=23=23=
=23=23=23=23=23=23=23=23=23=23=23=23=23=23=23=23=23=23=23=23=23=23=23=23=23=
=23=23=23=23=23=23=23=23=23=23

=23 CLAUSE: lib.locale.num.put

=23 NOTE (S2) (5 lines):
=23 TEXT: executing =22locale -a > /tmp/tmpfile-st2gNr=22
=23 CLAUSE: lib.locale.num.put
=23 FILE: process.cpp
=23 LINE: 274

=23 INFO (S1) (3 lines):
=23 TEXT: testing std::num_put<charT> with 1 thread, 200000 iterations =
each, in lo
cales =7B =22aa_DJ=22 =22aa_DJ.iso88591=22 =22aa_DJ.utf8=22 =22aa_ER=22 =
=22aa_ER=40saaho=22 =22aa_ER.utf8=22
 =22aa_ER.utf8=40saaho=22 =22aa_ET=22 =22aa_ET.utf8=22 =22af_ZA=22 =
=22af_ZA.iso88591=22 =22af_ZA.utf8=22 =22
am_ET=22 =22am_ET.utf8=22 =22an_ES=22 =22an_ES.iso885915=22 =
=22an_ES.utf8=22 =22ar_AE=22 =22ar_AE.iso885
96=22 =22ar_AE.utf8=22 =22ar_BH=22 =22ar_BH.iso88596=22 =22ar_BH.utf8=22 =
=22ar_DZ=22 =22ar_DZ.iso88596=22=20
=22ar_DZ.utf8=22 =22ar_EG=22 =22ar_EG.iso88596=22 =22ar_EG.utf8=22 =
=22ar_IN=22 =22ar_IN.utf8=22 =22ar_IQ=22=20
=7D
=23 CLAUSE: lib.locale.num.put

=23 INFO (S1) (3 lines):
=23 TEXT: exercising std::num_put<char>
=23 CLAUSE: lib.locale.num.put

=5BNew Thread 1084229952 (LWP 32194)=5D

Program received signal SIGSEGV, Segmentation fault.
=5BSwitching to Thread 1084229952 (LWP 32194)=5D
0x00002aaaaaafb027 in std::locale::locale ()
   from /home/mbrown/stdcxx-gcc-4.1.1-12D/lib/libstd12D.so
(gdb) where
=230  0x00002aaaaaafb027 in std::locale::locale ()
   from /home/mbrown/stdcxx-gcc-4.1.1-12D/lib/libstd12D.so
=231  0x0000000000403eea in thread_func ()
=232  0x00000039fae06305 in start_thread () from /lib64/libpthread.so.0
=233  0x00000039f82cd50d in clone () from /lib64/libc.so.6
=234  0x0000000000000000 in ?? ()


-- Mark


> -----Original Message-----
> From: sebor=40roguewave.com
> Sent: Mon, 18 Jun 2007 21:20:27 -0600
> To: stdcxx-dev=40incubator.apache.org
> Subject: status of thread safety tests
>=20
> I've been working on a document listing the thread safety tests
> in stdcxx/trunk and their current status:
>=20
>    http://people.apache.org/=7Esebor/thread_safety_tests.html
>=20
> The goal is to have a full understanding of all the problems
> and address them (or at least the most important ones) in the
> final 4.2.0 release.
>=20
> The document is still a work in progress, as is the test suite.
> Not all tests have been migrated from the Rogue Wave test suite
> in Perforce over to ASF Subversion. For those tests the links
> that point to the Perforce source repository won't work.