Hello,
  This little problem popped up again with the latest daily build preventing 
our active stereo cluster windows to work. I just had to add a range check back 
to hasExtension() in OSGWindow.inl and change the "vector<bool>" found in 
OSGWindow to "vector<UInt8>". Can someone add this to the trunk so it gets 
included in any future builds of 1.8? (even though we should all be moving to 
2.0 at this point) 

inline bool Window::hasExtension(UInt32 id)
{
+    if(id >= _availExtensions.size())
+        return false;
+    
     return _availExtensions[id];
}

Thanks

E.

---
Eric Maslowski
Research Computer Specialist 
University of Michigan 3D Lab
email: [EMAIL PROTECTED]


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carsten Neumann
Sent: Wednesday, September 05, 2007 19:26
To: [email protected]
Subject: Re: [Opensg-users] vector <x> iterator not dereferencable - OSG 1.8,VS 
2005, Run-time Error

        Hello Eric,

On Tue, 2007-09-04 at 09:35 -0400, Eric Maslowski wrote:
> Hello,
>   Replacing the "vector<bool>" with a "vector<Uint8>" fixed that 
> issue, but ran into another semi-related one. (see below) First, just 
> want to point out that there were a few instances of vector<bool> scattered 
> about. Some were:
> vector <bool    > for formatting purposes. (just in case this gets added to
> the standard release)
> 
> As for the other issue, I'm getting a vector out of range now in 
> RenderAction::start(id). Digging a little deeper shows that it's 
> actually coming from the "window->hasExtension(_arbOcclusionQuery)." 
> inside hasExtension(), _arbOcclusionQuery has id of 35, when total 
> count of entries in list (_availExtensions) is 35. Thus, causing out 
> of range error. This only seems to happen in a clustered application 
> when using more than one osg::viewport. (e.g. for stereo rendering)

hm, it might be a problem with concurrent access to the extension handling, but 
this is just a guess. I'll take a look at the extension handling from that 
angle.

> Unfortunately, I don't know enough about how OpenSG handles extensions 
> to be of much help here, but if someone has a work around/fix, I would 
> really appreciate it.

I imagine it would be possible to paper over the problem, by either finding out 
how to disable the range checks in the MS STL or use the attached patch (but 
that might disable an extension, although it is actually available), to get 
things going. 

> OpenSG 1.8 (daily build: Sep 2, 2007)
> NVIDIA Quadro 5600 (latest drivers)
> WinXP 64

        Thanks,
                Carsten
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users

Reply via email to