Date: Tue, 13 Dec 2022 09:28:47 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 268033] x11/xscreensaver: Crashing and dumping core on unlock Message-ID: <bug-268033-7141-wxJTIl3jp7@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-268033-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-268033-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=3D268033 --- Comment #3 from Duncan Bayne <duncan@bayne.id.au> --- This is proving tricky to debug :) I've added: WITH_DEBUG_PORTS=3Dx11/xscreensaver ... to /etc/make.conf, rebuilt xscreensaver, and I'm running it with lldb.= =20 However when the segfault happens it leaves the screen locked, preventing me from interacting further with lldb. I can unlock the system by switching to a different virtual console and kil= ling lldb, but that obviously stops the debugging session.=20=20 Anyways, this is what I've been able to glean so far: Process 35829 stopped * thread #1, name =3D 'xscreensaver-aut', stop reason =3D signal SIGSEGV: i= nvalid address (fault address: 0x0) frame #0: 0x000000080066fe84 libc.so.7`strlen + 84 libc.so.7`strlen: -> 0x80066fe84 <+84>: movq (%rdi), %r11 0x80066fe87 <+87>: leaq (%r11,%r8), %rcx 0x80066fe8b <+91>: notq %r11 0x80066fe8e <+94>: andq %r11, %rcx ((lldb) Terminated (Terminated here is when I kill lldb from the virtual console). --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-268033-7141-wxJTIl3jp7>