stdcxx-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Sebor (JIRA)" <>
Subject [jira] Commented: (STDCXX-826) [Sun C++] SIGABRT in istringstream example
Date Mon, 07 Apr 2008 20:03:25 GMT


Martin Sebor commented on STDCXX-826:

>From the stack trace it looks to me like the {{mbstate_t}} object that {{wfilebuf}} passes
to the {{codecvt}} facet isn't properly initialized. We're pretty careful about initializing
the stream state in the library so my suspicion is that the compiler isn't initializing it
correctly. The [POD_ZERO_INIT.cpp|]
config test tries to detect compiler bugs in this area. You might want to check to see if
the test passes and if it does, that the compiler really does initialize PODs correctly (e.g.,
by tweaking the test according to how {{mbstate_t}} is being initialized in {{wfilebuf}} and
elsewhere in the library -- look for the macros {{\_RWSTD_MBSTATE_T}} and {{\_RWSTD_NO_POD_ZERO_INIT}}.

> [Sun C++] SIGABRT in istringstream example
> ------------------------------------------
>                 Key: STDCXX-826
>                 URL:
>             Project: C++ Standard Library
>          Issue Type: Bug
>          Components: Examples
>    Affects Versions: 4.2.0
>         Environment: Sun C++/Solaris (both AMD64 and SPARC)
>            Reporter: Martin Sebor
>            Assignee: Eric Lemings
>             Fix For: 4.2.1
>   Original Estimate: 4h
>  Remaining Estimate: 4h
> When compiled with Sun C++ on Solaris, the example program [istringstream.cpp|]
abends with SIGABRT at runtime. Observed intermittently in 11D, 15D, and 15S builds both in
4.2.0 results and in those with the head of trunk.

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

View raw message