Skip to content
This repository has been archived by the owner on Apr 17, 2022. It is now read-only.

Crashes in glcSaveGLState #3818

Closed
wzdev-ci opened this issue Dec 3, 2012 · 11 comments
Closed

Crashes in glcSaveGLState #3818

wzdev-ci opened this issue Dec 3, 2012 · 11 comments

Comments

@wzdev-ci
Copy link
Contributor

wzdev-ci commented Dec 3, 2012

resolution_fixed type_bug | by raycast


Freshly compiled WZ master would crash for me, until I applied attached patch.
The crash happens in glGetPointerv, so I wrapped it in a check whether it actually is needed. Now warzone starts, I havn't tested much more.


Issue migrated from trac:3818 at 2022-04-16 10:44:20 -0700

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Dec 3, 2012

raycast uploaded file wz-gl.diff (1.7 KiB)

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Dec 3, 2012

vexed commented


This patch should be sent upstream to the quesoGLC people on sourceforge.

What video card & OS do you have anyway, drivers seems to be reporting the vertex arrays incorrectly ?
Also, you may want to modify it slightly

if (inGLState->vertexArray)

is good enough.

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Dec 3, 2012

vexed changed blocking which not transferred by tractive

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Dec 3, 2012

vexed changed blockedby which not transferred by tractive

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Dec 4, 2012

raycast commented


I belive not trusting GL_TRUE to be C true would be good style.

I'm on Linux and intel. It worked a few weeks before, but apparently some recent mesa/SDL/intel-driver/something update or git-pull changed this.

I don't think my graphics driver is reporting the vertex array incorrectly. I belive just the return value is undefined when a disabled feature is retrieved. Of course, retrieving a feature that was disabled doesn't make much sense anyway.

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Dec 6, 2012

Cyp commented


#3822 probably duplicate of this.

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Dec 8, 2012

Cyp commented


Sent upstream — http://quesoglc.git.sourceforge.net/git/gitweb.cgi?p=quesoglc/quesoglc;a=commit;h=e2f382d

The 0.7 release branch wasn't patched, but doesn't seem to be any corresponding code to patch, anyway.

@wzdev-ci
Copy link
Contributor Author

cybersphinx changed status from new to closed

@wzdev-ci
Copy link
Contributor Author

cybersphinx changed resolution from `` to fixed

@wzdev-ci
Copy link
Contributor Author

cybersphinx commented


Applied in 78a13deb19537497f15fc118ca5f501389a3e90b.

@wzdev-ci
Copy link
Contributor Author

Per commented


This patch creates new problems. See #3834

@wzdev-ci wzdev-ci mentioned this issue Apr 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant