Hi Sebastian,

[EMAIL PROTECTED] wrote:
> Hi,
> 
> thats actually what I did.
> I fetched the sourceforge code from last friday, compiled it with  
> scons and MSVS 2005. I didn´t use the dailybuild, that was a wrong info.
> Then I built the testTerrain linking with OSGContrib.lib/OSGContribD.lib.
> 
> While executing I receive an Assertion that "Expression: vector  
> subscript out of range"
> 
> Maybe its a problem with the MSVS 2005 compiler.
> 
> VS8 is stricter ( and more correct ) in catching bugs with std::vector

Yup, that could be it.

> vector::reserve(n) does not change the size of the vector. It only a
> request for allocation of additional memory. vector::size() is unchanged
> by reserve(). (from http://www.sgi.com/tech/stl/Vector.html)
> 
> other developper had the same error when using code like
> 
>> vector::reserve(n);
> 
> but instead
> 
>> vector::reserve(n);
>> vector::resize(n);

That has always been the case. But VS8 is much stricter than that: you can't 
even create an iterator to an illegal entry, by in general is not a problem if 
it's not used.

> I could imagine that this could happen during the initialization of  
> GeoPositions3f in OSGTerrain. But this is just my guess, I'm not  
> familiar enough with OpenSG.

Absolutely possible. What happens when you run with the debugger and OpenSG 
debug lkibs, can you get a line where the failure happens?

> But maybe somebody else has a comment on that.
> 
> Would it be helpful to recompile OpenSG using stlport instead??

That would probably work around it, but it would be better if we could fix the 
actual problem.

        Dirk


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users

Reply via email to