From owner-freebsd-gnome@FreeBSD.ORG Sun Nov 30 22:01:38 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 2B94116A4CF for ; Sun, 30 Nov 2003 22:01:38 -0800 (PST) Received: from smtp1.jp.viruscheck.net (smtp1.jp.viruscheck.net [154.33.69.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id E8D1B43FBD for ; Sun, 30 Nov 2003 22:01:35 -0800 (PST) (envelope-from bland@freebsd.org) Received: from scan3.jp.viruscheck.net ([154.33.69.38] helo=mail5.jp.viruscheck.net) by smtp1.jp.viruscheck.net with esmtp (Exim 3.36 #1) id 1AQh7m-0002RV-00; Mon, 01 Dec 2003 15:01:34 +0900 Received: from [220.220.111.152] (helo=noc.orchid) by mail5.jp.viruscheck.net with esmtp (Exim 3.36 #2) id 1AQh7m-0003mk-00; Mon, 01 Dec 2003 15:01:34 +0900 Received: from FreeBSD.org (horse.orchid [89.60.10.11]) by noc.orchid (8.12.9p2/8.12.9) with ESMTP id hB161O4v017770; Mon, 1 Dec 2003 15:01:25 +0900 (JST) (envelope-from bland@FreeBSD.org) Message-ID: <3FCAD934.8050707@FreeBSD.org> Date: Mon, 01 Dec 2003 15:01:24 +0900 From: Alexander Nedotsukov User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jeremy Messenger References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-gnome@FreeBSD.org Subject: Re: gnome-system-monitor (2.5.1) crashed on 5.2-BETA 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: Mon, 01 Dec 2003 06:01:38 -0000 Jeremy Messenger wrote: > To reproduce is... just run it and it will crash. Here's backtraces: > > ================================= > $ gdb gnome-system-monitor > > (gdb) r > Starting program: /usr/X11R6/bin/gnome-system-monitor > LibGTop-Server: recv: Resource temporarily unavailable > > Program received signal SIGPIPE, Broken pipe. > 0x28c186cf in write () from /lib/libc.so.5 > > (gdb) bt > #0 0x28c186cf in write () from /lib/libc.so.5 > #1 0x28461c7f in _write () from /usr/lib/libc_r.so.5 > #2 0x28461dc5 in write () from /usr/lib/libc_r.so.5 > #3 0x282efb5c in glibtop_write_l (server=0x282f2260, size=675734976, > buf=0x0) > at write.c:49 > #4 0x282ef40a in glibtop_call_l (server=0x282f2260, command=2, > send_size=0, > send_buf=0x20, recv_size=32, recv_buf=0xbfbfe950) at command.c:55 > #5 0x282efe2d in glibtop_get_cpu_l (server=0x282f2260, buf=0xbfbfe950) > at lib.c:63 > #6 0x08054780 in load_graph_new (type=0, procdata=0x809e300) > at load-graph.c:377 > #7 0x080510b0 in create_sys_view (procdata=0x809e300) at interface.c:379 > #8 0x080522ec in create_main_window (procdata=0x809e300) at > interface.c:620 > #9 0x0805064e in main (argc=134865664, argv=0x80a0140) at procman.c:535 > #10 0x0804ed39 in _start () > ================================= > > Let me know if you think I should report to Gnome Bugzilla. Jeremy, From this backtrace I can only say that actual problem not in g-s-m itself but in libgtop2. Looks like at this point libgtop_server2 gcrashed for some reason. This SIGPIPE just an indication that communication pipe to it get lost. Of course it also have a sence to do better error handling in g-s-m. To see where it crashes please run cont from the gdb prompt till you get some serious signal like SIGABRT/BUS etc delivered. I think it will be some kind of assert(). All the best, Alexander. > > Cheers, > Mezz > >