This is the mail archive of the
mailing list for the Insight project.
Re: Adding new target in Targetselection.itb
- From: Keith Seitz <keiths at redhat dot com>
- To: msarasa at fh-konstanz dot de
- Cc: "insight at sources dot redhat dot com" <insight at sources dot redhat dot com>
- Date: 02 Jul 2003 07:26:52 -0700
- Subject: Re: Adding new target in Targetselection.itb
- References: <firstname.lastname@example.org> <email@example.com>
> On Tue, 2003-07-01 at 04:38, firstname.lastname@example.org wrote:
> > set gdb_target(remote,pretty-name) "Remote/Serial"
> > set gdb_target(remotetcp,pretty-name) "Remote/TCP"
> > set gdb_target(remote,pretty-name) "Remote/Simuart_e1"
> > But the problem is that this overwrites the Remote serial option. This way
> > just Simuart and TCP are displayed in the option box menu.
You've noticed by now that the target selection is a little primitive.
It really doesn't do an adequate job of identifying debug protocols (ARM
angel, gdb's remote protocol, etc) and tranports (tcp, serial).
What you have defined is a new transport layer. If you look carefully at
the code snippet above, you'll notice that you've overwritten the
database name of the remote protocol over a serial line. Both your
entries and the Remote/Serial entires use the database identifier
"remote". Notice how Remote/TCP uses "remotetcp". I think that if you
simply change the name from "remote" to "remotesimuart" or something,
you should get both.
If this doesn't work, I've a few other ideas about what might be causing
trouble, but let's start with the simplest for now.