Part of the Khronos Group
OpenGL.org

The Industry's Foundation for High Performance Graphics

from games to virtual reality, mobile phones to supercomputers

Results 1 to 5 of 5

Thread: Program crashes at glCheckFramebufferStatusEXT while EXT_framebuffer_object present

  1. #1
    Newbie Newbie
    Join Date
    Sep 2017
    Posts
    3

    Program crashes at glCheckFramebufferStatusEXT while EXT_framebuffer_object present

    Hi , I am using EXT_framebuffer_object extension to capture buffer contents and it works on windows as well as Linux with NVIDIA latest drivers(opengl version 4.5).
    But when I connect to Linux machine through telnet which shows Mesa 1.4 and EXT_framebuffer_object extension is present, it crashes exactly at line glCheckFramebufferStatusEXT after rendering is started with glDrawBuffer(<Attachemnet point>). It is not even getting caught in catch. Please suggest possible ways to overcome this issue.
    Thanks.

  2. #2
    Member Regular Contributor
    Join Date
    Jul 2012
    Posts
    429
    Quote Originally Posted by Sheetald View Post
    Hi , I am using EXT_framebuffer_object extension to capture buffer contents and it works on windows as well as Linux with NVIDIA latest drivers(opengl version 4.5).
    But when I connect to Linux machine through telnet which shows Mesa 1.4 and EXT_framebuffer_object extension is present, it crashes exactly at line glCheckFramebufferStatusEXT after rendering is started with glDrawBuffer(<Attachemnet point>). It is not even getting caught in catch. Please suggest possible ways to overcome this issue.
    Thanks.
    And was these extension function pointers correctly/succesfully loaded (with using glew or with using something like glXGetProcAddressARB) ?
    Note this issue might have other reasons as well (ie the fact that you access a foreign machine with telnet for example).

  3. #3
    Newbie Newbie
    Join Date
    Sep 2017
    Posts
    3

    Yes, function pointers are checked with GLEW

    Yes, function pointers are checked with GLEW and it does not show NULL.
    How to check if they are correctly set or not? And how to prevent use of this extension (because extension is present).
    If we check if machine is remotely connected and prevent use of FBO extension then that will be wrong as when we change setting of connection tool(Exceed/MobaXterm) to 'Use Hardware rendering' it works without any issue.(as then it picks client machine's opengl version string - 4.5).

  4. #4
    Senior Member OpenGL Guru Dark Photon's Avatar
    Join Date
    Oct 2004
    Location
    Druidia
    Posts
    4,173
    Quote Originally Posted by Sheetald View Post
    Hi , I am using EXT_framebuffer_object extension to capture buffer contents and it works on windows as well as Linux with NVIDIA latest drivers(opengl version 4.5).

    But when I connect to Linux machine through telnet which shows Mesa 1.4 and EXT_framebuffer_object extension is present, it crashes... function pointers are checked with GLEW and it does not show NULL.
    Since this is a problem that occurs when running with Mesa3D GL drivers, you should probably ask for suggestions on the Mesa3D-users mailing list.

    Here's a random websearch hit that may be related to your problem: link

  5. #5
    Newbie Newbie
    Join Date
    Sep 2017
    Posts
    3
    Quote Originally Posted by Dark Photon View Post
    Since this is a problem that occurs when running with Mesa3D GL drivers, you should probably ask for suggestions on the Mesa3D-users mailing list.

    Here's a random websearch hit that may be related to your problem: link

    Thank you for the suggestions.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •