Sign in to follow this  
qrcrist

OpenGL GLDrawElements Access Violation Issue

Recommended Posts

qrcrist    103
I am working on an opengl project and I have been running into access violation errors. I managed to isolate the error into the code below, but I do not understand why it errors. Any help would be appreciated.

BTW: I know that the genbuffers and deletebuffers are used in a dumb way. The code below just replicates the error.
[CODE]
#include <gl/glew.h>
#include <gl/glut.h>
void draw()
{
glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT);
glLoadIdentity();
glEnableClientState(GL_VERTEX_ARRAY);
float v[]={
0,0,0,
1,1,1,
2,2,2,
};
unsigned char i[]={
0,1,2
};
unsigned int a;
unsigned int b;
glGenBuffers(1,&a);
glGenBuffers(1,&b);
glBindBuffer(GL_ARRAY_BUFFER,a);
glBindBuffer(GL_ELEMENT_ARRAY_BUFFER,b);
glBufferData(GL_ARRAY_BUFFER,36,v,GL_STATIC_DRAW);
glBufferData(GL_ELEMENT_ARRAY_BUFFER,3,i,GL_STATIC_DRAW);
glVertexPointer(3,GL_FLOAT,0,0);
glDrawElements(GL_TRIANGLES,3,GL_UNSIGNED_BYTE,0);
glDeleteBuffers(1,&a);
glDeleteBuffers(1,&b);
glBegin(GL_LINES);
glVertex3f(0,0,0);
glVertex3f(0,0,0);
glEnd();
glutSwapBuffers();
}
int window;
int width,height;
void changeSize(int w, int h)
{
if(h == 0)
h = 1;
double ratio = 1.0* w / h;
glMatrixMode(GL_PROJECTION);
glLoadIdentity();
glViewport(0, 0, w, h);
gluPerspective(45,ratio,.01f,1000);
glMatrixMode(GL_MODELVIEW);
width = w;
height = h;
}
void initWindow()
{
glEnable(GL_CULL_FACE);
glDepthFunc(GL_LEQUAL);
glEnable(GL_DEPTH_TEST);
glClearColor(0.1f,0.1f,0.1f,1);
glEnableClientState(GL_VERTEX_ARRAY);
}
int main(int argc, char **argv)
{
glutInit(&argc, argv);
glutInitDisplayMode(GLUT_DEPTH | GLUT_DOUBLE | GLUT_RGBA);
glutInitWindowSize(800,600);
window = glutCreateWindow("OpenGl");
glewInit();
initWindow();

glutIdleFunc(draw);
glutDisplayFunc(draw);
glutReshapeFunc(changeSize);
glutMainLoop();
return 0;
}
[/CODE]

Thanks,
Qcrist Edited by qrcrist

Share this post


Link to post
Share on other sites
mv348    263
I only had time for a quick glance, but it looks like you're assuming floats are 4 bytes, and unsigned chars are 1 byte. Seems reasonable but are you sure?

Also, the order in which you're calling bindBuffer and bufferData makes me uncomfortable. Maybe try:

bindBuffer( ... buffer 1 parameters)
bufferData( ... buffer 1 parameters)
bindBuffer( ... buffer 2 parameters)
bufferData( ... buffer 2 parameters)

because I think you are supposed to bind a given buffer immediately before calling bufferData. I don't know for sure since they're element, and vertex_array buffers, but it might be worht a shot.

I also think its weird that you are creating the buffers, filling them, rendering them, and then deleting the buffers all in one function. I assume this is some sort of test code to get things working but that kind defeats the point of having VBOs. You should have one function initVBOs() that puts the data in the bufffers and then leaves them there. And your draw() function should just bind the buffers, setup the attribute pointers, and then call glDrawElements. I think it would make debugging a bit easier.

Share this post


Link to post
Share on other sites
qrcrist    103
[quote name='mv348' timestamp='1346534504' post='4975549']
I only had time for a quick glance, but it looks like you're assuming floats are 4 bytes, and unsigned chars are 1 byte. Seems reasonable but are you sure?
[/quote]
Yes, I checked.

[quote name='mv348' timestamp='1346534504' post='4975549']
Also, the order in which you're calling bindBuffer and bufferData makes me uncomfortable. Maybe try:

bindBuffer( ... buffer 1 parameters)
bufferData( ... buffer 1 parameters)
bindBuffer( ... buffer 2 parameters)
bufferData( ... buffer 2 parameters)

because I think you are supposed to bind a given buffer immediately before calling bufferData. I don't know for sure since they're element, and vertex_array buffers, but it might be worht a shot.
[/quote]
didnt' work :[

[quote name='mv348' timestamp='1346534504' post='4975549']
I also think its weird that you are creating the buffers, filling them, rendering them, and then deleting the buffers all in one function. I assume this is some sort of test code to get things working but that kind defeats the point of having VBOs. You should have one function initVBOs() that puts the data in the bufffers and then leaves them there. And your draw() function should just bind the buffers, setup the attribute pointers, and then call glDrawElements. I think it would make debugging a bit easier.
[/quote]
Yeah, i'm doing that in the project code. But the error seems heap corruption somewhere in the code above.
The problem also goes away if I use shorts instead of chars for indices...?

[quote name='Sponji' timestamp='1346535542' post='4975554']
Tested the code here on Linux and seems to run just fine.
[/quote] Cool thanks

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Similar Content

    • By povilaslt2
      Hello. I'm Programmer who is in search of 2D game project who preferably uses OpenGL and C++. You can see my projects in GitHub. Project genre doesn't matter (except MMO's :D).
    • By ZeldaFan555
      Hello, My name is Matt. I am a programmer. I mostly use Java, but can use C++ and various other languages. I'm looking for someone to partner up with for random projects, preferably using OpenGL, though I'd be open to just about anything. If you're interested you can contact me on Skype or on here, thank you!
      Skype: Mangodoor408
    • By tyhender
      Hello, my name is Mark. I'm hobby programmer. 
      So recently,I thought that it's good idea to find people to create a full 3D engine. I'm looking for people experienced in scripting 3D shaders and implementing physics into engine(game)(we are going to use the React physics engine). 
      And,ye,no money =D I'm just looking for hobbyists that will be proud of their work. If engine(or game) will have financial succes,well,then maybe =D
      Sorry for late replies.
      I mostly give more information when people PM me,but this post is REALLY short,even for me =D
      So here's few more points:
      Engine will use openGL and SDL for graphics. It will use React3D physics library for physics simulation. Engine(most probably,atleast for the first part) won't have graphical fron-end,it will be a framework . I think final engine should be enough to set up an FPS in a couple of minutes. A bit about my self:
      I've been programming for 7 years total. I learned very slowly it as "secondary interesting thing" for like 3 years, but then began to script more seriously.  My primary language is C++,which we are going to use for the engine. Yes,I did 3D graphics with physics simulation before. No, my portfolio isn't very impressive. I'm working on that No,I wasn't employed officially. If anybody need to know more PM me. 
       
    • By Zaphyk
      I am developing my engine using the OpenGL 3.3 compatibility profile. It runs as expected on my NVIDIA card and on my Intel Card however when I tried it on an AMD setup it ran 3 times worse than on the other setups. Could this be a AMD driver thing or is this probably a problem with my OGL code? Could a different code standard create such bad performance?
    • By Kjell Andersson
      I'm trying to get some legacy OpenGL code to run with a shader pipeline,
      The legacy code uses glVertexPointer(), glColorPointer(), glNormalPointer() and glTexCoordPointer() to supply the vertex information.
      I know that it should be using setVertexAttribPointer() etc to clearly define the layout but that is not an option right now since the legacy code can't be modified to that extent.
      I've got a version 330 vertex shader to somewhat work:
      #version 330 uniform mat4 osg_ModelViewProjectionMatrix; uniform mat4 osg_ModelViewMatrix; layout(location = 0) in vec4 Vertex; layout(location = 2) in vec4 Normal; // Velocity layout(location = 3) in vec3 TexCoord; // TODO: is this the right layout location? out VertexData { vec4 color; vec3 velocity; float size; } VertexOut; void main(void) { vec4 p0 = Vertex; vec4 p1 = Vertex + vec4(Normal.x, Normal.y, Normal.z, 0.0f); vec3 velocity = (osg_ModelViewProjectionMatrix * p1 - osg_ModelViewProjectionMatrix * p0).xyz; VertexOut.velocity = velocity; VertexOut.size = TexCoord.y; gl_Position = osg_ModelViewMatrix * Vertex; } What works is the Vertex and Normal information that the legacy C++ OpenGL code seem to provide in layout location 0 and 2. This is fine.
      What I'm not getting to work is the TexCoord information that is supplied by a glTexCoordPointer() call in C++.
      Question:
      What layout location is the old standard pipeline using for glTexCoordPointer()? Or is this undefined?
       
      Side note: I'm trying to get an OpenSceneGraph 3.4.0 particle system to use custom vertex, geometry and fragment shaders for rendering the particles.
  • Popular Now