This is the mail archive of the insight@sourceware.org mailing list for the Insight project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Adding new target type


Robert S. Grimes wrote:
And of course, this works:

(gdb) target rtems-remote 192.168.1.55:2159

at least with gdb only.

Fooey.


Any other ideas?

Ah, I think I know what it could be... You wrote:


  # 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) {}

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.

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]