[sldev] [VWR] Crashes in C++ STL functions

[Erik Anderson]

To add to this, I ran into an STL crashing bug in a destructor recently and
figured out that the destructor was getting called twice.  An STL collection
should never contain NULL references inside of itself...

On 9/20/07, Dale Glass <dale at daleglass.net> wrote:
>
> On Thursday 20 September 2007 07:47:03 Ben Byer wrote:
> > ... etc.  I'd be happy to dig into these crashes more, but I don't
> > really even know where to begin -- I don't know where to find the code
> > that implements the crashing functions.   Help!
> > -b
> Crashes in the STL are like crashes in malloc: A real bug in the STL or
> malloc would be a very rare thing. The most likely reason for a crash
> there is that the code calling the STL function or malloc screwed
> something up, and then the function you called choked on it.
>
> At first glance, I see there in the stack: LLImageGL::~LLImageGL. This
> means something went wrong in the destructor. You could start by checking
> what that destructor does and what could go wrong in it.
>
> _______________________________________________
> Click here to unsubscribe or manage your list subscription:
> /index.html
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.secondlife.com/pipermail/sldev/attachments/20070920/af70ddec/attachment.htm