stdcxx-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Lemings (JIRA)" <j...@apache.org>
Subject [jira] Commented: (STDCXX-811) [Solaris Threads] SIGSEGV in 22.locale.statics.mt.cpp
Date Mon, 31 Mar 2008 17:00:26 GMT

    [ https://issues.apache.org/jira/browse/STDCXX-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583747#action_12583747
] 

Eric Lemings commented on STDCXX-811:
-------------------------------------

Woops.  Wrong thread model.  Nvm.

> [Solaris Threads] SIGSEGV in 22.locale.statics.mt.cpp
> -----------------------------------------------------
>
>                 Key: STDCXX-811
>                 URL: https://issues.apache.org/jira/browse/STDCXX-811
>             Project: C++ Standard Library
>          Issue Type: Bug
>          Components: 22. Localization
>    Affects Versions: 4.2.0
>            Reporter: Martin Sebor
>            Assignee: Eric Lemings
>            Priority: Critical
>             Fix For: 4.2.1
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> Regardless of the compiler (gcc or Sun C++), when compiled with Solaris Threads instead
of POSIX threads, the [22.locale.statics.mt|http://svn.apache.org/repos/asf/stdcxx/trunk/tests/localization/22.locale.statics.mt.cpp]
fails at runtime with SIGSEGV or SIGHUP, suggesting a problem with the uses of Solaris threads
mutexes in the library.
> I'm assuming this is not a regression but we need to check the results of the test in
4.2.0 to make sure. If it is one, it would make the priority of this issue a Blocker. Otherwise,
if it's not a new problem, we might be able to defer it post 4.2.1 if it's too hard to fix.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message