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 20:33:00 -0000 [thread overview]
Message-ID: <46DF127A.4050905@ll.mit.edu> (raw)
In-Reply-To: <46DF05C6.7060409@redhat.com>
Keith Seitz wrote:
> Robert S. Grimes wrote:
>> target rtems-remote 192.168.1.55:2159
>>
>
> This should be pretty easy. You're essentially trying to do just what
> gdb's built-in Remote/TCP target does. Take a look at this target in
> the target database in gdb/gdbtk/library/targetselection.itb.
>
Hi Keith,
Right, should be - that's what I was hoping for! I looked at the file
you referenced, and made these changes
<snip>
# Remote
<snip>
set gdb_target(remotetcp,pretty-name) "Remote/TCP"
set gdb_target(remotetcp,defbaud) "TCP"
set gdb_target(remotetcp,baud-rates) {}
set gdb_target(remotetcp,cmd) "remote tcpX"
set gdb_target(remotetcp,runlist) {1 1 0 1}
set gdb_target(remotetcp,after_attaching) {}
# RTEMS Remote - NEW!
set gdb_target(rtemsremotetcp,pretty-name) "RTEMS Remote/TCP"
set gdb_target(rtemsremotetcp,defbaud) "TCP"
set gdb_target(rtemsremotetcp,baud-rates) {}
set gdb_target(rtemsremotetcp,cmd) "rtems-remote tcpX"
set gdb_target(rtemsremotetcp,runlist) {1 1 0 1}
set gdb_target(rtemsremotetcp,after_attaching) {}
Then I rebuilt and installed ("make && make install"). Didn't seem to
make any difference, so I did a "make clean" in the gdb/gdbtk directory,
and tried again. Make worked a bit harder, but the results are the same
- no new target.
Looking in the file you mentioned, there are a whole lot of targets!
Many more than I have ever seen. So, I must be missing the magic step
where I specify which targets to include in the build, right? How is
that done?
Thanks!
-Bob
> Keith
>
>
next prev parent reply other threads:[~2007-09-05 20:33 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 [this message]
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
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=46DF127A.4050905@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).