stdcxx-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Lemings (JIRA)" <>
Subject [jira] Commented: (STDCXX-811) [Solaris Threads] SIGSEGV in
Date Mon, 31 Mar 2008 23:22:24 GMT


Eric Lemings commented on STDCXX-811:

Since the failure occurs in 64-bit builds and I have LD_LIBRARY_PATH_64 set in my environment
but the Makefile does not invoke the test program with this environment variable, I highly
suspect the failure is due to not setting the LD_LIBRARY_PATH_64 environment variable.

I temporarily modified the makefile.rules to test this theory.  The test is still running:
either its a long test ("with 2 threads, 20000 iterations each, in 16 locales" could take
a while) or its stuck in an indefinite loop.

> [Solaris Threads] SIGSEGV in
> -----------------------------------------------------
>                 Key: STDCXX-811
>                 URL:
>             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 [|]
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.

View raw message