Re: 945GM crash

2009-12-09 Thread Svilen
Hi Ian, > I should be able to look at it this weekend. I'll see if I can > reproduce it here. > Did you have a chance to look at the issue? Any success reproducing it? -- Return on Information: Google Enterprise Sear

Re: 945GM crash

2009-12-04 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Svilen wrote: > Ian, > > Thanks again. It seems that we agree on the initialization sequence, but > there are still some details - see below. > On 12/04/2009 10:07 PM, Ian Romanick wrote: >> >>> 2. You call glXGetProcedureAddress to get the valid exis

Re: 945GM crash

2009-12-04 Thread Svilen
Ian, Thanks again. It seems that we agree on the initialization sequence, but there are still some details - see below. On 12/04/2009 10:07 PM, Ian Romanick wrote: 2. You call glXGetProcedureAddress to get the valid existing entry points to the openGL procedures for the context you obtained

Re: 945GM crash

2009-12-04 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Svilen wrote: > On 12/03/2009 09:18 PM, Ian Romanick wrote: >>> I was also a bit confused by the glewinfo report that the driver >>> supports both glGenBuffers and glGenBuffersARB. It seems logical those >>> two entry points to end-up with the same fun

Re: 945GM crash

2009-12-04 Thread Svilen
On 12/03/2009 09:18 PM, Ian Romanick wrote: >> It was another suggestion in the GLEW thread - that the graphic context >> might be invalid. The application does have checks for this, but I'll >> try to reconfirm with the user that this is not the case. >> > This is easy enough to test. Run t

Re: 945GM crash

2009-12-03 Thread Svilen
On 12/03/2009 09:18 PM, Ian Romanick wrote: >> I was also a bit confused by the glewinfo report that the driver >> supports both glGenBuffers and glGenBuffersARB. It seems logical those >> two entry points to end-up with the same function. Besides (again from >> the glewinfo report) it seems strang

Re: 945GM crash

2009-12-03 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Svilen wrote: > I was also a bit confused by the glewinfo report that the driver > supports both glGenBuffers and glGenBuffersARB. It seems logical those > two entry points to end-up with the same function. Besides (again from > the glewinfo report

Re: 945GM crash

2009-12-03 Thread Svilen
Hi, I was also a bit confused by the glewinfo report that the driver supports both glGenBuffers and glGenBuffersARB. It seems logical those two entry points to end-up with the same function. Besides (again from the glewinfo report) it seems strange that all openGL 1.5 functions are supported y

Re: 945GM crash

2009-12-03 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Wilson wrote: > On Wed, 02 Dec 2009 00:17:06 +, Svilen > wrote: >> Hi guys, >> >> A bug reported initially here (Fedora 12) >> https://bugzilla.redhat.com/show_bug.cgi?id=541879 >> >> You can see from the bug reports that it involves "Mesa

Re: 945GM crash

2009-12-02 Thread Chris Wilson
On Wed, 02 Dec 2009 00:17:06 +, Svilen wrote: > Hi guys, > > A bug reported initially here (Fedora 12) > https://bugzilla.redhat.com/show_bug.cgi?id=541879 > > You can see from the bug reports that it involves "Mesa DRI Intel(R) 945GM > GEM 20090712 2009Q2 RC3" driver. > > The application

945GM crash

2009-12-01 Thread Svilen
Hi guys, A bug reported initially here (Fedora 12) https://bugzilla.redhat.com/show_bug.cgi?id=541879 and then replicated here (Toped) http://code.google.com/p/toped/issues/detail?id=21&colspec=ID%20Type%20Summary%20Component%20OpSys%20Owner%20Status%20Priority