* Multiple ~/.gdbtkinit files
@ 2003-10-20 18:55 Duane Ellis
2003-10-20 19:00 ` Keith Seitz
0 siblings, 1 reply; 6+ messages in thread
From: Duane Ellis @ 2003-10-20 18:55 UTC (permalink / raw)
To: insight
I've got a problem - we have numerous version of Insight - going all
the way back to when it was known as "GDBTK"
Each of these are for different target types.
Problem is - each and every one of them want to own the file
.gdbtkinit in your home directory.
And - each of these have slightly different formats that keep the
others from working.
The only solution we've come across is to alway start GDB with a
script that erases this file...
Sucks but it works.
With emacs - I've gotten around this (I run 4 different versions of
emacs depending on the platform I'm on) - I have a common .emacs file
that calculates a new .emacs-VERSION-PLATFORM-WHATEVER filename and
loads it.
Has any concideration been given to (A) Specifying this filename with
a command line option, or (B) - trying first a 'version specific
filename' then trying the normal filename?
-Duane.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Multiple ~/.gdbtkinit files
2003-10-20 18:55 Multiple ~/.gdbtkinit files Duane Ellis
@ 2003-10-20 19:00 ` Keith Seitz
2003-10-20 19:50 ` Duane Ellis
0 siblings, 1 reply; 6+ messages in thread
From: Keith Seitz @ 2003-10-20 19:00 UTC (permalink / raw)
To: duane; +Cc: insight
On Mon, 2003-10-20 at 11:54, Duane Ellis wrote:
> Has any concideration been given to (A) Specifying this filename with
> a command line option, or (B) - trying first a 'version specific
> filename' then trying the normal filename?
Goofy. So you have, for instance, different window geometries and open
windows based on the target? Right now these are all saved in the
target-independent preferences sections.
Anyway, you could try something like:
insight -nx --command=SCRIPT
Keith
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Multiple ~/.gdbtkinit files
2003-10-20 19:00 ` Keith Seitz
@ 2003-10-20 19:50 ` Duane Ellis
2003-10-20 19:57 ` Keith Seitz
0 siblings, 1 reply; 6+ messages in thread
From: Duane Ellis @ 2003-10-20 19:50 UTC (permalink / raw)
To: insight
>> 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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Multiple ~/.gdbtkinit files
2003-10-20 19:50 ` Duane Ellis
@ 2003-10-20 19:57 ` Keith Seitz
2003-10-20 20:10 ` Duane Ellis
0 siblings, 1 reply; 6+ messages in thread
From: Keith Seitz @ 2003-10-20 19:57 UTC (permalink / raw)
To: duane; +Cc: insight
On Mon, 2003-10-20 at 12:50, Duane Ellis wrote:
> >> 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.
Doh, you're right. That's not what you wanted. My bad.
> >> So you have, for instance, different window geometries and open
> windows based on the target?
>
> Not that I know of.
So what is conflicting that you need multiple .gdbtkinit files? [My
memory of preferences is slipping away, so be gentle. :-)]
> 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.
Hmmm. I thought that one could always work around the problem one of two
ways (on *nix, at least):
1. use lots of "dbug" statements and set GDBTK_LOGFILE (or is it
GDBTK_DEBUG? both? I don't recall). Using a log file would get you
output sooner (as I seem to recall).
2. Use "puts stdout" or "puts stderr" to force output to console. (This
doesn't work on cygwin, though.)
Keith
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Multiple ~/.gdbtkinit files
2003-10-20 19:57 ` Keith Seitz
@ 2003-10-20 20:10 ` Duane Ellis
2003-10-20 20:16 ` Keith Seitz
0 siblings, 1 reply; 6+ messages in thread
From: Duane Ellis @ 2003-10-20 20:10 UTC (permalink / raw)
To: keiths; +Cc: insight
>> So what is conflicting that you need multiple .gdbtkinit files? [My
We have 3 different internal Insight targets - all custom ports to
internally developed custom cpus.. one of them - was used our eBookman
product. Perhaps you saw this a couple years ago.
>> 1. use lots of "dbug" statements and set GDBTK_LOGFILE (or is it
GDBTK_DEBUG? both? I don't recall). Using a log file would get you
output sooner (as I seem to recall).
Where do I do this at?
I could sure use this right now - I'm fighting a problem with CYGWIN
where the source window stops working.
>> 2. Use "puts stdout" or "puts stderr" to force output to console. (This
doesn't work on cygwin, though.)
Agh... I know.... what a pain.
-Duane.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Multiple ~/.gdbtkinit files
2003-10-20 20:10 ` Duane Ellis
@ 2003-10-20 20:16 ` Keith Seitz
0 siblings, 0 replies; 6+ messages in thread
From: Keith Seitz @ 2003-10-20 20:16 UTC (permalink / raw)
To: duane; +Cc: insight
On Mon, 2003-10-20 at 13:10, Duane Ellis wrote:
> >> So what is conflicting that you need multiple .gdbtkinit files? [My
>
> We have 3 different internal Insight targets - all custom ports to
> internally developed custom cpus.. one of them - was used our eBookman
> product. Perhaps you saw this a couple years ago.
Yeah, I recall something about that. Nonetheless, the preferences should
not be conflicting with each other, EXCEPT if you are specifying, for
example, that the windows open or their geometries are different with
each target. The preferences system has understood about different
target specifications for quite some time. [I guess I am still not clear
what problem you need to overcome and why you would need multiple pref
files.]
> >> 1. use lots of "dbug" statements and set GDBTK_LOGFILE (or is it
> GDBTK_DEBUG? both? I don't recall). Using a log file would get you
> output sooner (as I seem to recall).
>
> Where do I do this at?
In the environment before starting up insight. See
gdbtk/library/main.tcl (look for GDBTK_DEBUGFILE or something like
that).
> >> 2. Use "puts stdout" or "puts stderr" to force output to console. (This
> doesn't work on cygwin, though.)
>
> Agh... I know.... what a pain.
Yeah, but sometimes it's all there is for the debugging of startup
problems. :v(
Keith
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2003-10-20 20:16 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-10-20 18:55 Multiple ~/.gdbtkinit files Duane Ellis
2003-10-20 19:00 ` Keith Seitz
2003-10-20 19:50 ` Duane Ellis
2003-10-20 19:57 ` Keith Seitz
2003-10-20 20:10 ` Duane Ellis
2003-10-20 20:16 ` Keith Seitz
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).