• State Accepted Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 1 reply
  • Subscribers 137 subscribers
  • Views 6112 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

eglMakeCurrent or eglGetCurrentDisplay bug?

Jason Wilkins

After calling eglMakeCurrent(m_display, EGL_NO_SURFACE, EGL_NO_SURFACE, EGL_NO_CONTEXT), the functions eglGetCurrentDisplay() returns EGL_NO_DISPLAY.  Is this the correct behavior?

When using ANGLE eglGetCurrentDisplay returns m_display.  This seems correct.

Parents
  • +1 Arm Employee Badge

    This is not a bug in our driver but mandated by the EGL specification.

    See 3.7.4 Context Queries:

    If there is no current context for the current rendering API, EGL_NO_DISPLAY is returned (this is not an error).

    By calling eglMakeCurrent with EGL_NO_CONTEXT as last parameter you are leaving the current thread without a current context.

Reply
  • +1 Arm Employee Badge

    This is not a bug in our driver but mandated by the EGL specification.

    See 3.7.4 Context Queries:

    If there is no current context for the current rendering API, EGL_NO_DISPLAY is returned (this is not an error).

    By calling eglMakeCurrent with EGL_NO_CONTEXT as last parameter you are leaving the current thread without a current context.

Children
No data