Date: Thu, 13 Dec 2012 22:58:49 +0100 From: Niclas Zeising <zeising@freebsd.org> To: Johannes Dieterich <dieterich.joh@gmail.com> Cc: freebsd-current@freebsd.org, Dimitry Andric <dim@FreeBSD.org> Subject: Re: new xorg segfault 11 with KMS Message-ID: <50CA4F99.3060106@freebsd.org> In-Reply-To: <50CA4D3D.3040401@gmail.com> References: <CABquGzXefGp%2BD0qmaAboYQSGip-4A3XwQUT7M%2BMfVqSZjQ6i9Q@mail.gmail.com> <50CA4A58.7070109@FreeBSD.org> <50CA4D3D.3040401@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/13/12 22:48, Johannes Dieterich wrote: > On 12/13/12 16:36, Dimitry Andric wrote: >> On 2012-12-13 21:49, Johannes Dieterich wrote: >>> I lately see xorg segfault 11s with CURRENT, WITH_NEW_XORG=yes and >>> WITH_KMS=yes. Interestingly, gdm loads fine but xfce4 at login directly >>> causes the segfault (log attached), gnome survives a bit longer but >>> starting any bigger application (e.g. firefox) causes it to crash with >>> the >>> same log. >>> >>> I have a Xorg.core file, but since it is without debug symbols the >>> backtrace makes little sense to me. >> >> Please post the backtrace anyway. :-) Or recompile xorg-server with >> WITH_DEBUG=yes in your environment, and reproduce the crash. > Here we go: > > I also rebuild xorg with debug enabled. Interestingly, I cannot > reproduce the crash anymore. Either I forgot to rebuild something (seems > unlikely) or the crash has to do with optimizations or flags not present > in a debug build. This is not unlikely. There are probably places in the X codebase which depends on gcc specific behavior, or undefined behavior, by accident or by chance. Regards -- Niclas Zeising
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50CA4F99.3060106>