[
https://issues.apache.org/jira/browse/STDCXX-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587246#action_12587246
]
elemings edited comment on STDCXX-828 at 4/9/08 9:28 AM:
-------------------------------------------------------------
Yeah I've narrowed down the test case to just the test that exercises the long
double type for char streams with UserTraits. As for the function arguments,
they aren't shown in either the stack trace shown by the assertion or the
debugger. The stack trace in the debugger looks like this:
{noformat}
...
[5] rw_vasnprintf(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0x427617
[6] rw_asnprintf(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0x42d240
[7] _rw_fmtflags(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0x433bac
[8] _rw_pvasnprintf(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0x426cb4
[9] _rw_fmtexpr(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0x42ca20
[10] _rw_pvasnprintf(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0x426cb4
[11] rw_vasnprintf(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0x427587
[12] _rw_vfprintf(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0x42d6f3
...
{noformat}
Do you know off-hand if Sun C++ supports optimized debug builds (a la GCC)? If
so and the failure still occurs with this build, it'd be a lot easier to
analyze. Currently, I'm just using plain ol' print statements.
was (Author: elemings):
Yeah I've narrowed down the test case to just the test that exercises the
long double type for wide character streams. As for the function arguments,
they aren't shown in either the stack trace shown by the assertion or the
debugger. The stack trace in the debugger looks like this:
{noformat}
...
[5] rw_vasnprintf(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0x427617
[6] rw_asnprintf(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0x42d240
[7] _rw_fmtflags(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0x433bac
[8] _rw_pvasnprintf(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0x426cb4
[9] _rw_fmtexpr(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0x42ca20
[10] _rw_pvasnprintf(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0x426cb4
[11] rw_vasnprintf(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0x427587
[12] _rw_vfprintf(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0x42d6f3
...
{noformat}
Do you know off-hand if Sun C++ supports optimized debug builds (a la GCC)? If
so and the failure still occurs with this build, it'd be a lot easier to
analyze. Currently, I'm just using plain ol' print statements.
> [AMD64] SIGABRT in 27.istream.fmat.arith
> ----------------------------------------
>
> Key: STDCXX-828
> URL: https://issues.apache.org/jira/browse/STDCXX-828
> Project: C++ Standard Library
> Issue Type: Bug
> Components: Tests
> Affects Versions: 4.2.0
> Environment: Sun C++ 5.9/Solaris/AMD64
> Reporter: Martin Sebor
> Assignee: Eric Lemings
> Fix For: 4.2.1
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> When compiled with Intel C++ 10.0 on Linux/AMD64 or Sun C++ 5.9 on Solaris
> 10/AMD64, the test
> [27.istream.fmat.arith.cpp|http://svn.apache.org/repos/asf/stdcxx/trunk/tests/iostream/27.istream.fmat.arith.cpp]
> abends with SIGABRT. This was observed in 8{D,S}, 12{D,S} and 15D build
> types, not necessarily consistently on both platforms.
> The same test was also failing in 4.2.0 with Intel C++.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
