From: Keith Seitz <keiths@redhat.com>
To: George Najarian <najay@najay.com>
Cc: insight@sourceware.org
Subject: Re: CVS Insight running on Windows 7 x64 using ActiveTCL, mingw/msys, built for arm-none-eabi
Date: Fri, 09 Jul 2010 18:53:00 -0000 [thread overview]
Message-ID: <4C37701B.2020907@redhat.com> (raw)
In-Reply-To: <4C376D11.9080604@najay.com>
On 07/09/2010 11:40 AM, George Najarian wrote:
> What do I do to get the debug symbols included?
If you need to debug Tcl code, there is some stuff in the sources to
allow this, but I've never used it, and I don't know if it works at all.
I usually do this the old-fashioned "printf"-like way.
> Does Insight have a built in TCL prompt or trace window?
Yes. See the README for details. I usually use either GDBTK_DEBUGFILE or
GDBTK_DEBUG. I've not tried/used GDBTK_TRACE. YMMV.
You can access the Tcl interpreter using the console command "tk". You
can open a debug window after you start insight (i.e. GDBTK_DEBUG = 0)
by typing at the console:
(gdb) tk ManagedWin::open DebugWin
Errors will show up in orange with "E", Info messages are green with
"I", and warnings will be yellow (I think) with "W".
I seem to recall fixing some target settings dialog issues before...
What does "show version" display?
My guess is this has something to do with the way COM ports are probed.
That's what it was last time, as I recall.
Keith
next prev parent reply other threads:[~2010-07-09 18:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 18:40 George Najarian
2010-07-09 18:53 ` Keith Seitz [this message]
2010-07-09 20:48 ` George Najarian
2010-07-09 21:10 ` Keith Seitz
2010-07-10 7:34 ` George Najarian
2010-07-10 14:28 ` George Najarian
2010-07-13 4:12 ` Gene Smith
2010-07-10 4:34 ` Gene Smith
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=4C37701B.2020907@redhat.com \
--to=keiths@redhat.com \
--cc=insight@sourceware.org \
--cc=najay@najay.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).