From stdcxx-dev-return-1159-apmail-incubator-stdcxx-dev-archive=incubator.apache.org@incubator.apache.org Thu Mar 30 17:50:17 2006 Return-Path: Delivered-To: apmail-incubator-stdcxx-dev-archive@www.apache.org Received: (qmail 41973 invoked from network); 30 Mar 2006 17:50:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 30 Mar 2006 17:50:17 -0000 Received: (qmail 94816 invoked by uid 500); 30 Mar 2006 17:50:17 -0000 Delivered-To: apmail-incubator-stdcxx-dev-archive@incubator.apache.org Received: (qmail 94802 invoked by uid 500); 30 Mar 2006 17:50:17 -0000 Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: stdcxx-dev@incubator.apache.org Delivered-To: mailing list stdcxx-dev@incubator.apache.org Received: (qmail 94791 invoked by uid 99); 30 Mar 2006 17:50:16 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Mar 2006 09:50:16 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [208.30.140.160] (HELO moroha.quovadx.com) (208.30.140.160) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Mar 2006 09:50:16 -0800 Received: from bco-exchange.bco.roguewave.com (bco-exchange.bco.roguewave.com [172.19.31.48]) by moroha.quovadx.com (8.13.4/8.13.4) with ESMTP id k2UHnME3031500 for ; Thu, 30 Mar 2006 17:49:22 GMT Received: from [10.70.2.6] (skynet.bco.roguewave.com [10.70.2.6]) by bco-exchange.bco.roguewave.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id HQZ7JH1Z; Thu, 30 Mar 2006 10:47:57 -0700 Message-ID: <442C1A60.6080300@roguewave.com> Date: Thu, 30 Mar 2006 10:50:24 -0700 From: Liviu Nicoara User-Agent: Thunderbird 1.5 (X11/20051201) MIME-Version: 1.0 To: stdcxx-dev@incubator.apache.org Subject: Re: std::locale mt test failing References: <4D6A8407B7AC6F4D95B0E55C4E7C4C6203EEA6A4@exmsk.moscow.vdiweb.com> <44299862.8060007@roguewave.com> <442C0FFA.2010302@roguewave.com> <442C1123.3000202@roguewave.com> <442C1225.4000502@roguewave.com> <442C13A5.6010708@roguewave.com> <442C19A3.2060801@roguewave.com> In-Reply-To: <442C19A3.2060801@roguewave.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Yep, with SunPro it is getting a shorter one but it shows too t_cancel and thr_exit_common (in 4.1.4 though). Martin Sebor wrote: > Liviu Nicoara wrote: >> I got it. I will test against dev and file a bug report only if that >> fails too. > > It does with gcc but I haven't been able to reproduce it with Sun > C++ yet. The stack trace I got with my optimized build isn't very > helpful: > > (gdb) where > #0 0xff3c26d8 in ?? () > #1 0xff3c3330 in ?? () > #2 0xff3c5dc0 in ?? () > #3 0xff3c5ec4 in ?? () > #4 0xff13fd88 in _t_cancel () from /usr/lib/libc.so.1 > #5 0xff13c81c in _thr_exit_common () from /usr/lib/libc.so.1 > > Martin > >> Thanks, >> Liviu >> >> Martin Sebor wrote: >> >>> Liviu Nicoara wrote: >>> >>>> Liviu Nicoara wrote: >>>> >>>> >>>>> The following test case fails intermittently with SIGSEGV: >>>>> ........... >>>>> I will file a JIRA incident soon. >>>> Will 4.1.4 be revisited and the bug addressed if dev does not show the >>>> problem? What is the policy in this case? >>> I don't plan to fix anything but showstoppers in the upcoming (Rogue >>> Wave SourcePro 9 Update 1) release. I'm also not planning to release >>> stdcxx 4.1.4. The next stdcxx release will be either 4.2 or 5.0 >>> depending on if we decide to break binary compatibility. >>> >>> Martin >>> >