From: Keith Seitz <keiths@redhat.com>
To: duane@franklin.com
Cc: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Re: Multiple ~/.gdbtkinit files
Date: Mon, 20 Oct 2003 19:57:00 -0000 [thread overview]
Message-ID: <1066680027.1583.47.camel@lindt.uglyboxes.com> (raw)
In-Reply-To: <200310201950.h9KJo5L19370@europa.franklin.com>
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
next prev parent reply other threads:[~2003-10-20 19:57 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
2003-10-20 19:57 ` Keith Seitz [this message]
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=1066680027.1583.47.camel@lindt.uglyboxes.com \
--to=keiths@redhat.com \
--cc=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).