nvoglnt.dll access violation question

  • Follow


Hello,
I'm programming an OpenGL based application in VC++ 6.0 under WinXP
sp1.
I'm working on an Asus mobo, 865, 678 MB RAM, 2.4 Ghz, my graphics
card is FX 5200 128 MB by Abit.
My nvoglnt.dll version is 6.14.10.5303  .
My problem is that sometimes I get an access violation exception from
a thread running on the nvoglnt.dll module (not the main thread).
It causes the program to crash of course.
The AV is thrown randomly regardless of any specific action I do in my
code.
I used a global exception filter and got the following information :

Code of exception : 0xC0000005 .
Address in module : 0x695FE09B .
Frame : 054E6DBC .
Logical Address : 0001:000FD09B .


I get that behavior also with nvoglnt.dll version 6.14.10.6177 , I
don't know about addresses from that file yet though.

Thanx,
Noam.
0
Reply noam_b 11/17/2004 3:30:06 PM

"noam" <noam_b@yahoo.com> wrote in message
news:a447b8e3.0411170730.511a2567@posting.google.com...
> Hello,
> I'm programming an OpenGL based application in VC++ 6.0 under WinXP
> sp1.
> I'm working on an Asus mobo, 865, 678 MB RAM, 2.4 Ghz, my graphics
> card is FX 5200 128 MB by Abit.
> My nvoglnt.dll version is 6.14.10.5303  .
> My problem is that sometimes I get an access violation exception from
> a thread running on the nvoglnt.dll module (not the main thread).
> It causes the program to crash of course.
> The AV is thrown randomly regardless of any specific action I do in my
> code.
> I used a global exception filter and got the following information :
>
> Code of exception : 0xC0000005 .
> Address in module : 0x695FE09B .
> Frame : 054E6DBC .
> Logical Address : 0001:000FD09B .
>
>
> I get that behavior also with nvoglnt.dll version 6.14.10.6177 , I
> don't know about addresses from that file yet though.
>
> Thanx,
> Noam.

Do you have an active context in that thread? You can't access a single
context
from multiple threads. OpenGL is *not* thread-safe.

jbw


0
Reply JB 11/18/2004 1:53:22 AM


hi
i only have one thread in my program that uses OpenGL commands (the
main thread).
the other threads i have are only simple worker threads that has
nothing to do with graphics.

Noam.

"JB West" <jbwest@NOSPAM_acm.org> wrote in message news:<mPednYVPYrHonQHcRVn-gw@comcast.com>...
> "noam" <noam_b@yahoo.com> wrote in message
> news:a447b8e3.0411170730.511a2567@posting.google.com...
> > Hello,
> > I'm programming an OpenGL based application in VC++ 6.0 under WinXP
> > sp1.
> > I'm working on an Asus mobo, 865, 678 MB RAM, 2.4 Ghz, my graphics
> > card is FX 5200 128 MB by Abit.
> > My nvoglnt.dll version is 6.14.10.5303  .
> > My problem is that sometimes I get an access violation exception from
> > a thread running on the nvoglnt.dll module (not the main thread).
> > It causes the program to crash of course.
> > The AV is thrown randomly regardless of any specific action I do in my
> > code.
> > I used a global exception filter and got the following information :
> >
> > Code of exception : 0xC0000005 .
> > Address in module : 0x695FE09B .
> > Frame : 054E6DBC .
> > Logical Address : 0001:000FD09B .
> >
> >
> > I get that behavior also with nvoglnt.dll version 6.14.10.6177 , I
> > don't know about addresses from that file yet though.
> >
> > Thanx,
> > Noam.
> 
> Do you have an active context in that thread? You can't access a single
> context
> from multiple threads. OpenGL is *not* thread-safe.
> 
> jbw
0
Reply noam_b 11/20/2004 4:48:08 PM

noam wrote:

> hi
> i only have one thread in my program that uses OpenGL commands (the
> main thread).
> the other threads i have are only simple worker threads that has
> nothing to do with graphics.
>

The OpenGL implementation might use threads internally. This may be a 
bug in the driver or simply a not-very-helpful error message for a "bad" 
parameter.

Double check your OpenGL calls using glTrace or similar. (google for it, 
I don't have a URL handy.)

--
Andy V

0
Reply Andy 11/20/2004 5:01:06 PM

noam wrote:
> hi
> i only have one thread in my program that uses OpenGL commands (the
> main thread).
> 

Did you create the render context in the same
thread? I've had problems creating render
contexts in one thread then using them in
another.

If it's not that, maybe you have a bug in your
program.


-- 
<\___/>          For email, remove my socks.
/ O O \
\_____/  FTB.    The Cheat is not dead!


0
Reply fungus 11/21/2004 6:20:02 AM

4 Replies
455 Views

(page loaded in 0.689 seconds)

Similiar Articles:













7/23/2012 4:41:49 PM


Reply: