On Thu, 20 Mar 2008 19:44:43 -0600
Martin Sebor <[EMAIL PROTECTED]> wrote:
> Martin Sebor wrote:
> > Mark Wright wrote:
> >>> On Thu, 20 Mar 2008 09:26:19 -0600
> >>> Martin Sebor <[EMAIL PROTECTED]> wrote:
> >>> I couldn't reproduce the SEGV with 4.2.0 but I did reproduce it on
> >>> the head of trunk (both with Sun C++/Solaris and gcc/Linux). I
> >>> could reproduce the RUI in set::insert(). It turns out the RUI is
> >>> a known issue (http://issues.apache.org/jira/browse/STDCXX-87)
> >>> that hasn't been analyzed yet. I'm not sure it's related to the
> >>> SEGV. Let me spend some time on it today and get back to you.
> >> Hello Martin,
> >> Great, thanks.
> >>> Just to confirm: you're still using 4.2.0, correct?
> >> No, I built it from subversion yesterday.
> > Okay, that explains the SEGV. We've recently introduced a regression
> > on trunk that's causing the problem. We should have a fix for it
> > soon.
> Travis checked in a fix for the SEGV:
Great, thanks. I did an svn update to get the fix, rebuilt stdcxx,
and confirmed this fixes the SEGV, thanks.
> I've also made some progress on the RUI in set::insert(). My take
> on it is that it's probably a compiler bug. See the details here:
> I don't have a small test case to send to Sun and I'm not 100% sure
> it's benign so I'll see if there's a way to work around it other
> than by defining the copy assignment operator in std::pair (it
> may not be the most efficient solution). Check the issue for
Thanks. Just in case you wanted to report it to the Sun Compiler
team, here is the link: