Date: Mon, 01 Dec 2003 15:01:24 +0900 From: Alexander Nedotsukov <bland@FreeBSD.org> To: Jeremy Messenger <mezz7@cox.net> Cc: freebsd-gnome@FreeBSD.org Subject: Re: gnome-system-monitor (2.5.1) crashed on 5.2-BETA Message-ID: <3FCAD934.8050707@FreeBSD.org> In-Reply-To: <oprzhl3ngb8ckrg5@smtp.central.cox.net> References: <oprzhl3ngb8ckrg5@smtp.central.cox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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 > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3FCAD934.8050707>