Bug 69013 - piglit arb_debug_output-api_error regression
Summary: piglit arb_debug_output-api_error regression
Status: RESOLVED NOTABUG
Alias: None
Product: Mesa
Classification: Unclassified
Component: Mesa core (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: mesa-dev
QA Contact:
URL:
Whiteboard:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2013-09-06 04:40 UTC by Vinson Lee
Modified: 2013-09-06 06:10 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Vinson Lee 2013-09-06 04:40:07 UTC 
mesa: 505fad04f10eee1efdfcd8986b4d484b49d39986 (master)

$ ./bin/arb_debug_output-api_error -auto
Testing defaults.
Mesa: User error: GL_INVALID_ENUM in glEnable(0xffffffff)
  The log shouldn't be empty.
PIGLIT: {'result': 'fail' }

b5c4795f386976830370f56d1fa5a1c4099d88e2 is the first bad commit
commit b5c4795f386976830370f56d1fa5a1c4099d88e2
Author: Timothy Arceri <t_arceri@yahoo.com.au>
Date:   Mon Aug 26 19:02:11 2013 +1000

    mesa: Implement GL_DEBUG_OUTPUT
    
    Signed-off-by: Timothy Arceri <t_arceri@yahoo.com.au>
    
    Reviewed-by: Brian Paul <brianp@vmware.com>

:040000 040000 16d665093675355ad5a9eb65d6ab2f23f7ba959d d6e589f296276b95402ec161f0d6aa43056ae998 M	src
bisect run success
Comment 1 Timothy Arceri 2013-09-06 06:10:59 UTC 
This is my bad I forgot to submit a piglit patch to stop this fail report.

Explanation below:

* From the KHR_debug spec: "If the DEBUG_OUTPUT state is disabled then no
  messages are added to the message log." To allow for this the state of
  DEBUG_OUTPUT now affects the ARB_debug_output extension meaning
  callbacks and messages are now not called/stored unless either
  DEBUG_OUTPUT is enabled or CONTEXT_DEBUG_BIT_ARB is set. The existing
  Mesa implementation allowed callbacks/messages to be stored without
  CONTEXT_DEBUG_BIT_ARB being set.

I will submit a piglit patch later today.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.