From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20372 invoked by alias); 23 Jan 2006 10:34:17 -0000 Received: (qmail 20363 invoked by uid 22791); 23 Jan 2006 10:34:17 -0000 X-Spam-Check-By: sourceware.org Received: from bbnrelbas03.net.external.hp.com (HELO bbnrelbas03.bastion.europe.hp.com) (192.6.76.87) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 23 Jan 2006 10:34:15 +0000 Received: from demexg11.emea.cpqcorp.net (demexg11.emea.cpqcorp.net [16.41.86.138]) by bbnrelbas03.bastion.europe.hp.com (Postfix) with ESMTP id 8CB9E111; Mon, 23 Jan 2006 11:34:02 +0100 (CET) Received: from bbnexc02.emea.cpqcorp.net ([16.57.5.27]) by demexg11.emea.cpqcorp.net with Microsoft SMTPSVC(6.0.3790.211); Mon, 23 Jan 2006 11:34:01 +0100 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Problem running insight on Solaris 5.7 Date: Mon, 23 Jan 2006 10:34:00 -0000 Message-ID: <0295B57A4D11E44C94685AD72B2C5C850563968F@bbnexc02.emea.cpqcorp.net> From: "Lentes, Joern" To: "Keith Seitz" Cc: Mailing-List: contact insight-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sourceware.org X-SW-Source: 2006-q1/txt/msg00028.txt.bz2 =20 > > I managed to compile insight-weekly-6.40.50.20051212 after=20 > having troubles with older and stable versions. > > Also the install went fine, but I can run insight only as root. > > When I try to run it als normal user it just exits with=20 > code 1. When I start insight with option --tui --nw it works. > > I checked with ldd which shared libs insight is using and=20 > checked user permissions on these. Everything is ok. >=20 > Perhaps the permissions are set improperly on one of the=20 > libraries or something? Weird! I checked all the permissions of libraries that insight might need. And these are ok. > What's the exit code -- is it really just 1? Wow. You might=20 > have to try debugging insight on gdb, setting a break on=20 > exit(). That should at least allow you to find out what is=20 > causing the exit. Yes, the exit code is just 1. I started debugging insight, but I have to dig into the code to understand what it's doing. Here is the backtrace. (gdb) backtrace #0 0xff01a5a4 in exit () from /usr/lib/libc.so.1 #1 0x00059a5c in _start () (gdb)=20 Thanks, Joern