[PyOpenGL-Devel] [ pyopengl-Bugs-1266693 ] segfault when non-float arg to glColor4v()

[SourceForge.net <no...@so...>]

Bugs item #1266693, was opened at 2005-08-22 21:35
Message generated for change (Comment added) made by mcfletch
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105988&aid=1266693&group_id=5988

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Maciej Kalisiak (mackal)
>Assigned to: Mike C. Fletcher (mcfletch)
Summary: segfault when non-float arg to glColor4v()

Initial Comment:
"Bad things"(TM) happen when a non-float is passed to
glColor4v().  Specific case I ran into: by mistake I
happened to pass a somewhat complex class object as the
fourth element of the vector.  This caused a segfault
immediately (SDL parachute deployed, etc.)  I haven't
tested to see whether this occurs with the class object
in the other vector positions, but I imagine so, seeing
as how this is probably caused by Pyopengl passing the
arguments directly to OpenGL, without checking validity.


----------------------------------------------------------------------

>Comment By: Mike C. Fletcher (mcfletch)
Date: 2008-01-19 22:10

Message:
Logged In: YES 
user_id=34901
Originator: NO

Version 3.x guards against this and does not crash on tests with the
situation described.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105988&aid=1266693&group_id=5988