From: Keith Seitz <keiths@redhat.com>
To: "Lentes, Joern" <joern.lentes@hp.com>
Cc: insight@sourceware.org
Subject: Re: Problem running insight on Solaris 5.7
Date: Fri, 13 Jan 2006 19:10:00 -0000 [thread overview]
Message-ID: <43C7FB1D.7070703@redhat.com> (raw)
In-Reply-To: <0295B57A4D11E44C94685AD72B2C5C850558059C@bbnexc02.emea.cpqcorp.net>
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
next prev parent reply other threads:[~2006-01-13 19:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 8:50 Lentes, Joern
2006-01-13 19:10 ` Keith Seitz [this message]
2006-01-23 10:34 Lentes, Joern
2006-01-24 17:10 ` Keith Seitz
2006-01-25 9:19 Lentes, Joern
2006-01-25 10:04 Lentes, Joern
2006-01-25 15:06 ` Keith Seitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43C7FB1D.7070703@redhat.com \
--to=keiths@redhat.com \
--cc=insight@sourceware.org \
--cc=joern.lentes@hp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).