stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Sebor <se...@roguewave.com>
Subject Re: std::locale mt test failing
Date Thu, 30 Mar 2006 17:47:15 GMT
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
>>


Mime
View raw message