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