From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10962 invoked by alias); 13 Jan 2006 19:10:45 -0000 Received: (qmail 10953 invoked by uid 22791); 13 Jan 2006 19:10:44 -0000 X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 13 Jan 2006 19:10:40 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id k0DJAbOP017354; Fri, 13 Jan 2006 14:10:37 -0500 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id k0DJAW127657; Fri, 13 Jan 2006 14:10:32 -0500 Received: from [127.0.0.1] (sebastian-int.corp.redhat.com [172.16.52.221]) by pobox.corp.redhat.com (8.12.8/8.12.8) with ESMTP id k0DJAVPW013851; Fri, 13 Jan 2006 14:10:31 -0500 Message-ID: <43C7FB1D.7070703@redhat.com> Date: Fri, 13 Jan 2006 19:10:00 -0000 From: Keith Seitz User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929) MIME-Version: 1.0 To: "Lentes, Joern" CC: insight@sourceware.org Subject: Re: Problem running insight on Solaris 5.7 References: <0295B57A4D11E44C94685AD72B2C5C850558059C@bbnexc02.emea.cpqcorp.net> In-Reply-To: <0295B57A4D11E44C94685AD72B2C5C850558059C@bbnexc02.emea.cpqcorp.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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/msg00023.txt.bz2 Lentes, Joern wrote: > I managed to compile insight-weekly-6.40.50.20051212 after 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 code 1. When I start insight with option --tui --nw it works. > I checked with ldd which shared libs insight is using and checked user permissions on these. Everything is ok. Perhaps the permissions are set improperly on one of the libraries or something? Weird! What's the exit code -- is it really just 1? Wow. You might have to try debugging insight on gdb, setting a break on exit(). That should at least allow you to find out what is causing the exit. > How can I get more information out of insight, what the problem is? Does it right any logfiles? > Any help is welcome. If the debug system manages to load, setting GDBTK_DEBUG=2 in your environment will write a log file of the actually gui code (the tcl code). However, I'm betting you won't get that far. It sounds like gdbtk_init or something is bailing on you... Keith