Thank you for the followup.

Concerning your last backtrace: The crash is in a different thread than the=
 one
you mentioned, but the symbols in the backtrace suggest that it happens whi=
le
updating a buffer, so the crash is likely a consequence of the failed mmap =
and
the game not checking whether the map succeeded.

I'm noticing a lot of other error messages in stdout, though, such as the
"Failed to launch child process" and something about allocation f=
ailures that
is unrelated to Mesa. Perhaps the game's virtual address space is simply
getting full? It does call itself a 32 bit program.

I'm a bit surprised in hindsight that nodcc had an effect. Now that I think
about it, Hawaii doesn't actually have DCC, does it?