Bug 320 - improving DebugGL
Summary: improving DebugGL
Status: RESOLVED WONTFIX
Alias: None
Product: Jogl
Classification: JogAmp
Component: core (show other bugs)
Version: 1
Hardware: All all
: P3 enhancement
Assignee: Michael Bien
URL:
Depends on:
Blocks:
 
Reported: 2007-10-09 02:58 CEST by Sven Gothel
Modified: 2015-09-27 03:14 CEST (History)
0 users

See Also:
Type: FEATURE
SCM Refs:
Workaround: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sven Gothel 2010-03-24 07:50:52 CET 


---- Reported by mbien@fh-landshut.de 2007-10-09 14:58:22 ----

DebugGL could add additional checks to some methods.
e.g:
bounds checks for methods containing Buffers and indices as arguments (causing
often VM crash if out of bounds or not rewinded - and a lot of confusion for
beginners)



---- Additional Comments From kbr 2007-10-09 18:34:32 ----

Agreed. It would be helpful if you could look into enhancing GlueGen or the
BuildComposablePipeline class to autogenerate these kinds of range checks. There
are already some range checks for the simple cases, but I agree that more are
needed for best behavior. However it will be a while before the JOGL development
team has time to investigate this.




--- Bug imported by sgothel@jausoft.com 2010-03-24 07:50 EDT  ---

This bug was previously known as _bug_ 320 at https://jogl.dev.java.net/bugs/show_bug.cgi?id=320