[Bug 108787] [BSW] Mesa "total_needs <= urb_chunks" abort in GfxBench CarChase startup, if Mesa is built with Meson

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=108787

--- Comment #12 from Eero Tamminen <eero.t.tamminen at intel.com> ---
reply to Sergii Romantsov from comment #11)
> Could it be related to issue
> https://bugs.freedesktop.org/show_bug.cgi?id=109791?
> 
> So with meson < 0.46 asserts seems may be included into release-builds.

Meson 0.47.2 from Ubuntu 18.10 seems to work fine as-is in Ubuntu 18.04, so I
was able to do a Mesa built with a newer Meson version.

I'm still getting the assert though:
testfw_app: src/intel/common/gen_urb_config.c:152: gen_get_urb_config:
Assertion `total_needs <= urb_chunks' failed.


Then I tried Autotools build with --enable-debug.

It gives gives the same error, and additionally also:
Mesa: User error: GL_INVALID_ENUM in glGetString(GL_EXTENSIONS)


=> it's not a regression or Meson related, but an older issue on BSW.

This may actually explain bug 101406 i.e. why Mesa has never rendered CarChase
correctly on BSW.



(In reply to Dylan Baker from comment #9)
> Doesn't autotools only build with asserts with --enable-debug is set? Meson
> controls that separately from the buildtype with -Db_ndebug. Can you
> reproduce if you add `-Dbuildtype=release` to the meson command line? (as
> long as your meson is newer than 0.45 asserts are defaulted to off when the
> buildtype is release or plain)

I don't get assert with "release".  As've I stated above, I was using
"debugoptimized".

FYI: I thought it corresponded to RELWITHDEBINFO target in CMake.  With CMake,
there's the RELEASE build type that strips the binaries, and RELWITHDEBINFO,
which builds with debug symbols and doesn't do stripping i.e. binaries are 100%
match to release, just with debug info.

According to Meson docs, "release" build doesn't include debug symbols, but
according to "file" command it doesn't strip binaries either.  Meson
documentation doesn't say anything about "debugoptimized" enabling asserts:
  https://mesonbuild.com/Running-Meson.html

So I'm not sure whether that's a bug or not.

=> With what Meson options I'm supposed to get Mesa binaries that correspond to
release build (no asserts), just with full (-g) debug symbols?


PS. IMHO Meson --help output or manual page should explain the differences
between the build targets.  Currently it doesn't seem to be properly documented
even in latest Meson docs.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20190307/4d79da31/attachment.html>