From: Keith Seitz <keiths@redhat.com>
To: "Bhagat, Vivek" <vivek.bhagat@scr.siemens.com>
Cc: "'insight@sources.redhat.com'" <insight@sources.redhat.com>
Subject: Re: insight GUI not working!
Date: Fri, 16 Jul 2004 13:17:00 -0000 [thread overview]
Message-ID: <1089984004.2768.8.camel@lindt.uglyboxes.com> (raw)
In-Reply-To: <20B20848358CDA44AB6A2E277D2E1C5E0569723E@postoffice.scr.siemens.com>
On Fri, 2004-07-16 at 06:03, Bhagat, Vivek wrote:
> I am running insight-5.2.1-249 on SuSE 9 Pro and I have all the tools need to run the debugger. But the problem is insight only works for only one user account and for rest of my user account when I run it from the shell window, I only get the gdb console window and GUI does not open up.
> Is it something with my insight configuration that is prohibiting other users to open up insight GUI?
> If anyone can help me out with this it will be a great help?
When you say "gdb console window" what do you mean? You get command-line
gdb in your terminal window or you get Insight's Console Window but no
source window? I'll assume it's the former and not the latter.
[Actually, if it is the latter, try erasing your ~/.gdbtkinit file.]
Are there any errors displayed when insight is started from a
non-working account? Is DISPLAY set?
Perhaps it is a permissions problem with the installation?
I just cannot think of any other reason why an X application would run
for one user and not another. This isn't windows, after all. ;-)
Keith
next prev parent reply other threads:[~2004-07-16 13:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-16 13:03 Bhagat, Vivek
2004-07-16 13:17 ` Keith Seitz [this message]
2004-07-16 13:31 Bhagat, Vivek
2004-07-16 13:43 ` Keith Seitz
2004-07-16 14:07 Bhagat, Vivek
2004-07-16 14:39 ` 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=1089984004.2768.8.camel@lindt.uglyboxes.com \
--to=keiths@redhat.com \
--cc=insight@sources.redhat.com \
--cc=vivek.bhagat@scr.siemens.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).