Date: 09 Jul 2002 16:14:47 -0700 From: Joe Kelsey <joe@zircon.seattle.wa.us> To: Joe Marcus Clarke <marcus@marcuscom.com> Cc: Joe Kelsey <joek@mail.flyingcroc.net>, freebsd-gnome <freebsd-gnome@FreeBSD.ORG> Subject: Re: Debugging gdm2 Message-ID: <1026256488.60775.35.camel@zircon.zircon.seattle.wa.us> In-Reply-To: <1026246030.17789.7.camel@gyros.marcuscom.com> References: <3D2B3374.5040704@flyingcroc.net> <1026246030.17789.7.camel@gyros.marcuscom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2002-07-09 at 13:20, Joe Marcus Clarke wrote: > Find the process that's spinning after you enter your username, then > attach gdb to it. You should then be able to get a backtrace. I attached to the gdm subprocess, and found it stuck in run_pictures(). Is gdm supposed to use up 80-90% of the cpu? It seems to be stuck in this run_pictures loop after forking gdmlogin. This seems wasteful. Apparantly, the problem is in gdmlogin, but I haven't debugged that yet. It appears to simply hang after reading the username. I haven't looked at the code yet, but it is possible that there is some pending interaction with gdmaskpass, but that doesn't seem to be running... I will attempt more later. /Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-gnome" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1026256488.60775.35.camel>