From owner-freebsd-current Fri Oct 2 05:57:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA20035 for freebsd-current-outgoing; Fri, 2 Oct 1998 05:57:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tokyonet-entrance.astec.co.jp (tokyonet-entrance.astec.co.jp [202.239.16.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA20025; Fri, 2 Oct 1998 05:57:37 -0700 (PDT) (envelope-from g-nakai@internetsolutions.co.jp) Received: from amont.astec.co.jp (amont.astec.co.jp [172.20.10.1]) by tokyonet-entrance.astec.co.jp (8.9.1+3.0W/3.7W-astecMX2.3) with ESMTP id VAA11738; Fri, 2 Oct 1998 21:57:20 +0900 (JST) Received: from apricot (isi05.astec.co.jp [172.20.12.205]) by amont.astec.co.jp (8.7.6/3.6W-astecMX2.4) with SMTP id VAA07985; Fri, 2 Oct 1998 21:57:19 +0900 (JST) Date: Fri, 2 Oct 1998 21:57:19 +0900 (JST) Message-Id: <199810021257.VAA07985@amont.astec.co.jp> From: =?ISO-2022-JP?B?GyRCQ2YwZhsoQg==?= =?ISO-2022-JP?B?GyRCOSxHbhsoQg==?= To: vanilla@FreeBSD.ORG Cc: current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: gnome projects & devel/libgtop In-Reply-To: <19980930234810.A5757@oneway.net> References: <19980930234810.A5757@oneway.net> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver 1.23 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Could someone can hack gnome* & devel/libgtop for 3.0c, > > the author of libgtop use 2.2.x, > > and there are too muck different between 2.2.x & 3.0. In general, the commands like top depends on kernel architecture heavily, so I think this is true, but there is something about the basic programming before that. A main process forks and execl /usr/X11R6/bin/libgtop_server and libgtop_server cause segmentation fault with signal 11 and die soon, ( see the console error message in your login prompt ) though libgtop_server alone from prompt doesn't die. It is from sample code in example directory, but applets seem to cause the same problem. I will see more in the source code in next week... -------------- Yukihiro Nakai To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message