From: "Robert S. Grimes" <rsg@ll.mit.edu>
To: Keith Seitz <keiths@redhat.com>
Cc: insight@sourceware.org
Subject: Re: Adding new target type
Date: Wed, 05 Sep 2007 21:46:00 -0000 [thread overview]
Message-ID: <46DF2397.5@ll.mit.edu> (raw)
In-Reply-To: <46DF1A96.3010603@redhat.com>
Keith Seitz wrote:
>
> This isn't going to work. Take a look at TargetSelection::fill_targets
> and TargetSelection::get_target_list. If you type "help target", you
> should get your target in the output. I'm guessing a line that looks
> like "target rtems-remote -- BLAH BLAH". The "rtems-remote" is the
> actual name of the target, and the one you need to use as the lead
> index in the target database instead of "rtemsremotetcp". The dummy
> "tcp" targets are for targets which have multiple connection
> possibilities.
Not really following you exactly, but... it works! Here's what I put there:
# RTEMS Remote
# set gdb_target(rtems-remote,pretty-name) "RTEMS Remote"
# set gdb_target(rtems-remote,defbaud) "38400"
# set gdb_target(rtems-remote,baud-rates) {9600 19200 38400 57600 115200}
# set gdb_target(rtems-remote,cmd) "rtems-remote com1"
# set gdb_target(rtems-remote,runlist) {1 1 0 1}
# set gdb_target(rtems-remote,after_attaching) {}
set gdb_target(rtems-remote,pretty-name) "RTEMS Remote/TCP"
set gdb_target(rtems-remote,defbaud) "TCP"
set gdb_target(rtems-remote,baud-rates) {}
set gdb_target(rtems-remote,cmd) "rtems-remote tcpX"
set gdb_target(rtems-remote,runlist) {1 1 0 1}
set gdb_target(rtems-remote,after_attaching) {}
When I open the Target Selection dialog now, I see "RTEMS Remote/TCP",
and when I select that, it gets pre-filled with 192.168.1.69, port 2159,
just like I want it to! Of course, I'm not sure where those host:port
values came from, but I'm guessing its some cache action on the part of
gdb, as that's the last target I attempted to - is that right?
Note from the above that I was also trying to get the serial setup to
work, but that presented one oddity - when I selected the serial RTEMS
target, the Baud value started out with "TCP" instead of 38400 - odd.
But don't worry, I don't want to use the serial port anyway, and even if
I did, I could live with that.
Thanks, Kevin!!!
-Bob
>
> See if that fixes anything. [It might help to put a "dbug" statement
> in TargetSelection::fill_targets so that you tell what it is doing.]
>
> Keith
>
>
next prev parent reply other threads:[~2007-09-05 21:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 19:32 Robert S. Grimes
2007-09-05 19:39 ` Keith Seitz
2007-09-05 20:33 ` Robert S. Grimes
2007-09-05 20:44 ` Keith Seitz
2007-09-05 20:56 ` Robert S. Grimes
2007-09-05 21:07 ` Keith Seitz
2007-09-05 21:46 ` Robert S. Grimes [this message]
2007-09-05 22: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=46DF2397.5@ll.mit.edu \
--to=rsg@ll.mit.edu \
--cc=insight@sourceware.org \
--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).