From owner-freebsd-gnome@FreeBSD.ORG Fri Dec 12 13:34:12 2003 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B21DB16A4CE for ; Fri, 12 Dec 2003 13:34:12 -0800 (PST) Received: from lakemtao08.cox.net (lakemtao08.cox.net [68.1.17.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0340243D36 for ; Fri, 12 Dec 2003 13:34:11 -0800 (PST) (envelope-from mezz7@cox.net) Received: from mezz.mezzweb.com ([68.103.32.11]) by lakemtao08.cox.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP id <20031212213408.CCPA5790.lakemtao08.cox.net@mezz.mezzweb.com>; Fri, 12 Dec 2003 16:34:08 -0500 Date: Fri, 12 Dec 2003 15:33:09 -0600 To: Piero References: <1071172308.749.43.camel@gyros> <20031212161854.50e5c7a0.piero@poprostu.pl> From: Jeremy Messenger Content-Type: text/plain; format=flowed; charset=iso-8859-1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: In-Reply-To: <20031212161854.50e5c7a0.piero@poprostu.pl> User-Agent: Opera7.23/Linux M2 build 518 cc: freebsd-gnome@freebsd.org Subject: Re: How do I debug the logout session? X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2003 21:34:12 -0000 On Fri, 12 Dec 2003 16:18:54 +0100, Piero wrote: > On Thu, 11 Dec 2003 14:31:21 -0600, Jeremy Messenger > wrote: > >> On Thu, 11 Dec 2003 14:51:48 -0500, Joe Marcus Clarke >> wrote: >> >> > On Thu, 2003-12-11 at 14:45, Jeremy Messenger wrote: >> >> I have everything up to date, it's Gnome 2.5.2 and it can't >> >logout. I am> wondering how can I debug that kind of bug? >> > >> > gnome-session is responsible for logging in and out. You might >> > want to attach gdb to that from a vty and see what happens. >> > Also, check the~/.xsession-errors and console for anything >> > useful. >> >> There's no ~/.xsession-errors and I don't understand or know what >> you mean by vty? Attaching the errors.txt is what I get from kill >> X by manual, but I don't think it will help that much. I tried to >> add that '--sync' in the .xinitrc like 'exec gnome-session --sync' >> and no luck. > > vty is a virtual terminal (ttyv), that's what you get besides the > console with Alt+F, before starting Xwindow (unless you start it > with display manager). When in Gnome try switching to it with > Ctrl+Alt+F - you should see teh same errors that would go to > ~/.xsession-errors, at least it works this way here. Ahh, vty is virtual terminal.. Thanks! I did that and it doesn't even storage the errors in the ~/.xsession-errors. How can I force that? Well, the vty doesn't work very well with Nvidia driver, which I can't come back to X. But, when I did the vty and I can use gdb, so I use gdb on gnome-session and I get like this: ============================ (gdb) bt #0 0x28c198ef in poll () from /lib/libc.so.5 #1 0x28a09961 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 #2 0x28a0937b in _thread_kern_scheduler () from /usr/lib/libc_r.so.5 #3 0xd0d0d0d0 in ?? () #4 0x7fffffff in ?? () Error accessing memory address 0xffffffff: Bad address. ============================ Do anyone have the same problem with the logout on today Gnome 2.5.x? Cheers, Mezz > I had sleepless night, so I hope I explained myself ;-) > > HTH, -- bsdforums.org 's moderator, mezz.