From: "Martin M. Hunt" <hunt@redhat.com>
To: "Liang, James" <jliang@sandia.gov>
Cc: "'insight@sources.redhat.com'" <insight@sources.redhat.com>
Subject: Re: Developing for Insight
Date: Thu, 10 Apr 2003 20:05:00 -0000 [thread overview]
Message-ID: <1050005115.1154.10.camel@Dragon> (raw)
In-Reply-To: <71251C7D5FB1D2119C8F0008C7A44ED103791FE6@es07snlnt.sandia.gov>
On Thu, 2003-04-10 at 12:46, Liang, James wrote:
> Hello. I am porting GDB and would like to make the port work with Insight.
> I had hoped to
> just get a the text version to work without having the work on Insight, but
> this is quickly becoming
> infeasible.
By "port" do you mean you are adding a new target to GDB? Or are you
porting it to a new host OS? Or both?
Which sources are you starting from?
> I'm only a few days into it, and I already have a case where the text
> version of GDB knows where I am
> (when I hit the where button, it shows the source files and line numbers),
> but the graphical version won't bring
> this info up in the window.
You should have gdb/gdbtk/library/help/debug.html. Take a look at
that. Set the environment variable "GDBTK_DEBUG" before running insight
then look for errors in the debug window. Add debug statements into the
tcl source as necessary.
See gdb/gdbtk/README for more information.
> What development environment did you guys use to debug the tcl code for
> Insight?
Just the internal debug window. It can trace or display the output of tcl debug statements.
>Is there a spec that tells which
> bits of Insight functionality depend on which data structures or which text
> GDB command?
Nothing more than the README file and inline comments.
Martin
next prev parent reply other threads:[~2003-04-10 20:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-10 19:47 Liang, James
2003-04-10 20:05 ` Martin M. Hunt [this message]
2003-04-21 22:23 Liang, James
2003-04-21 22:59 ` Martin M. Hunt
2003-04-22 16:53 Liang, James
2003-04-22 17:52 ` Keith Seitz
2003-04-22 18:18 Liang, James
2003-04-22 18:43 ` Keith Seitz
2003-04-22 18:37 Liang, James
2003-04-22 18:45 ` Keith Seitz
2003-04-22 20:39 Liang, James
2003-04-22 20:58 ` Keith Seitz
2003-04-22 20:52 Liang, James
[not found] <71251C7D5FB1D2119C8F0008C7A44ED103792014@es07snlnt.sandia.gov>
2003-04-22 21:18 ` Keith Seitz
[not found] <71251C7D5FB1D2119C8F0008C7A44ED103792015@es07snlnt.sandia.gov>
2003-04-22 21:45 ` Keith Seitz
2003-04-22 21:47 ` Keith Seitz
[not found] <71251C7D5FB1D2119C8F0008C7A44ED103792016@es07snlnt.sandia.gov>
2003-04-22 23:15 ` 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=1050005115.1154.10.camel@Dragon \
--to=hunt@redhat.com \
--cc=insight@sources.redhat.com \
--cc=jliang@sandia.gov \
/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).