From: Duane Ellis <duane@franklin.com>
To: insight@sources.redhat.com
Subject: Re: Multiple ~/.gdbtkinit files
Date: Mon, 20 Oct 2003 19:50:00 -0000 [thread overview]
Message-ID: <200310201950.h9KJo5L19370@europa.franklin.com> (raw)
In-Reply-To: <1066676597.1589.15.camel@lindt.uglyboxes.com> (message from Keith Seitz on 20 Oct 2003 12:03:17 -0700)
>> Anyway, you could try something like:
The -nx and --command options are not the problem, they deal with the
normal ".gdb<<blank-not-TK>>init" file.
I'm talking about the gdb<<TK>>init file (or gdbtk.ini file on
windows) there is no command line option to disable that one.
It is 100% handled by the prefs.tcl file.
It seems that if I delete this file - things work again when they
break. If I don't - things go horribly wrong.
>> So you have, for instance, different window geometries and open
windows based on the target?
Not that I know of.
The really tough thing is - I can't seem to debug tcl startup problems
under insight.
For instance, if you have a syntax error somewhere, or any erorr
message, it gets swallowed up and not shown to you. You have to debug
this stuff blind.
-- On a side note --
This problem is not limited to Insight - we have RH6.2 on some
machines, and RH7.3 on others. and we remote-X into them from other
machines. (Depends on where I am at my desk, or in the hardware lab,
etc)
What is a *REAL* pain in the but is when GNOME or KDE discovers that
you have an old "GNOME" init file - then upgrades it for you - then
you go to another machine and it won't start because it runs an older
version of GNOME.
Central to that problem is a shared home directory throughout our
systems. It's both a blessing and a curse.
Both RH6.2 and RH7.3 don't like it when you login 2 times via remote-X
from two different locations..... ie: You go into the hardware lab and
login, while remaining logged in at your desk)
-Duane.
next prev parent reply other threads:[~2003-10-20 19:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-20 18:55 Duane Ellis
2003-10-20 19:00 ` Keith Seitz
2003-10-20 19:50 ` Duane Ellis [this message]
2003-10-20 19:57 ` Keith Seitz
2003-10-20 20:10 ` Duane Ellis
2003-10-20 20:16 ` 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=200310201950.h9KJo5L19370@europa.franklin.com \
--to=duane@franklin.com \
--cc=insight@sources.redhat.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).