Date: Sun, 18 Dec 2022 12:34:40 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 268327] graphics/mesa-dri: 22.3.0 breaks direct rendering (radeon, SUMO, r600_dri) Message-ID: <bug-268327-7141-HxhwWVs0pe@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-268327-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-268327-7141@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D268327 --- Comment #20 from Florian Walpen <dev@submerge.ch> --- Created attachment 238898 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D238898&action= =3Dedit Valgrind log of Xorg segfault, verbose. Also I was able to get a trace of this in valgrind, attached here. It's ver= bose and kind of lengthy, search for "Invalid read". Backtrace is the same as the others, and the read address matches what I se= e in the core dump. What is interesting is the "Use of uninitialized value" just before the invalid read, at the same place in the stack. It suggests that t= he invalid read is a consequence of operating on uninitialized data, in the red-black-tree implementation of C++ std::set. Unless our standard library is seriously broken, this looks like a case for upstream mesa to me. It's their internal data structures with a custom allocator. Did anybody already report it there? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-268327-7141-HxhwWVs0pe>