[Mesa-dev] [Bug 10966] workaround to avoid the assert main/renderbuffer.c:2041: _mesa_add_renderbuffer:...
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Fri Jul 2 13:49:52 PDT 2010
https://bugs.freedesktop.org/show_bug.cgi?id=10966
Tom Fogal <tfogal at alumni.unh.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tfogal at alumni.unh.edu
--- Comment #12 from Tom Fogal <tfogal at alumni.unh.edu> 2010-07-02 13:49:51 PDT ---
We are hitting this with our application, VisIt, using software rendering with
OSMesa 7.8.2.
yana3{brugger}33: bin/visit
Running: gui -dv
Running: viewer -host 127.0.0.1 -port 5600 -dv -geometry 1512x1148+408+0
-borders 21,8,4,4 -shift 4,21 -preshift 0,0 -defer
Running: mdserver -host 127.0.0.1 -port 5601 -dv
Running: engine_ser -host 127.0.0.1 -port 5600 -dv
engine_ser: main/renderbuffer.c:1924: _mesa_add_renderbuffer: Assertion
`bufferName == BUFFER_DEPTH || bufferName == BUFFER_STENCIL ||
fb->Attachment[bufferName].Renderbuffer == ((void *)0)' failed.
Running: engine_ser -host 127.0.0.1 -port 5600 -dv
engine_ser: main/renderbuffer.c:1924: _mesa_add_renderbuffer: Assertion
`bufferName == BUFFER_DEPTH || bufferName == BUFFER_STENCIL ||
fb->Attachment[bufferName].Renderbuffer == ((void *)0)' failed.
This is with our current trunk. Mesa is built using the autoconf build system:
./configure \
CC="${C_COMPILER}" \
CXX="${CXX_COMPILER}" \
CFLAGS="${CFLAGS} -DUSE_MGL_NAMESPACE" \
CXXFLAGS="${CXXFLAGS} -DUSE_MGL_NAMESPACE" \
--prefix=${PF} \
--without-demos \
--with-driver=osmesa \
--disable-gallium \
--with-max-width=16384 \
--with-max-height=16384 \
--disable-glw \
--disable-glu \
--disable-egl
AFAIK, we don't actually use glRenderbuffer* in our application, so I guess
there is an implicit buffer for the implicit display?
More information as I know it...
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the mesa-dev
mailing list