[ http://issues.apache.org/jira/browse/STDCXX-87?page=all ]
Martin Sebor updated STDCXX-87:
-------------------------------
Fix Version: 4.2
(was: 4.1.4)
> [SunPro 5.7] RUI in std::set::insert()
> --------------------------------------
>
> Key: STDCXX-87
> URL: http://issues.apache.org/jira/browse/STDCXX-87
> Project: C++ Standard Library
> Type: Bug
> Components: 23. Containers
> Versions: 4.1.2
> Environment: SunPro 5.7/Solaris 10
> Reporter: Martin Sebor
> Assignee: Martin Sebor
> Fix For: 4.2
>
> This test case was distilled from the one posted in this thread:
> http://mail-archives.apache.org/mod_mbox/incubator-stdcxx-dev/200512.mbox/[EMAIL
> PROTECTED]
> $ cat t.cpp && nice gmake t && dbx -q t
> #include <set>
> int main()
> {
> std::set<int>().insert (0);
> }
> generating dependencies for t.cpp
> CC -c -D_RWSTDDEBUG -D_RWSTD_USE_CONFIG
> -I/build/sebor/sunpro-5.7.j4-11s/include -I/build/sebor/dev/stdlib/include
> -I/build/sebor/dev/stdlib/examples/include -library=%none -g +w t.cpp
> CC t.o -o t -library=%none -L/build/sebor/sunpro-5.7.j4-11s/lib
> -L/build/sebor/sunpro-5.7.j4-11s/lib -lstd11s -lm
> ^C^Chave seen 2 interrupts
> dbx: warning: wait for process 24188 failed -- Interrupted system call
> dbx: dbx interrupted!
> (dbx) check -all
> access checking - ON
> memuse checking - ON
> (dbx) run
> Running: t
> (process id 24234)
> RTC: Enabling Error Checking...
> RTC: Running program...
> Read from uninitialized (rui):
> Attempting to read 3 bytes at address 0xffbff821
> which is 265 bytes above the current stack pointer
> stopped in
> std::pair<__rw::__rw_debug_iter<__rw::__rb_tree<int,int,__rw::__ident<int,int>,std::less<int>,std::allocator<int>
>
> >,__rw::__rw_tree_iter<int,int,int*,int&,__rw::__rw_rb_tree_node<std::allocator<int>,int,int,__rw::__ident<int,int>
> >
> >,__rw::__rw_tree_iter<int,int,int*,int&,__rw::__rw_rb_tree_node<std::allocator<int>,int,int,__rw::__ident<int,int>
> > > >,bool>::operator= at 0x0001cd3c
> 0x0001cd3c: operator=+0x0024: ba,a 0x00049b3c ! 0x49b3c
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
