Skip to content

mis-handling of string sizes in lime_gl_get_active_attrib #1323

@mgambrell

Description

@mgambrell

std::string buffer (GL_ACTIVE_ATTRIBUTE_MAX_LENGTH, 0);

This function (and the C function following it) are full of misconceptions for how the buffer size should be managed. The problems begin in the line above (where a symbolic constant is used as a maximum buffer size which should be got with glGetProgram instead) but the function is full of problems as far as I can tell.

I can't suggest fixes because I can't test them readily. It's a long story.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions