From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 641 invoked by alias); 5 Sep 2007 21:46:16 -0000 Received: (qmail 633 invoked by uid 22791); 5 Sep 2007 21:46:15 -0000 X-Spam-Check-By: sourceware.org Received: from LLMAIL1.LL.MIT.EDU (HELO ll.mit.edu) (129.55.12.41) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 05 Sep 2007 21:46:09 +0000 Received: (from smtp@localhost) by ll.mit.edu (8.12.10/8.8.8) id l85LjxPB002560; Wed, 5 Sep 2007 17:45:59 -0400 (EDT) Received: from raisin.llan.ll.mit.edu( ), claiming to be "[155.34.70.97]" via SMTP by llpost, id smtpdAAAkEaa4e; Wed Sep 5 17:45:55 2007 Message-ID: <46DF2397.5@ll.mit.edu> Date: Wed, 05 Sep 2007 21:46:00 -0000 From: "Robert S. Grimes" User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Keith Seitz CC: insight@sourceware.org Subject: Re: Adding new target type References: <46DF045C.2080806@ll.mit.edu> <46DF05C6.7060409@redhat.com> <46DF127A.4050905@ll.mit.edu> <46DF1505.4070107@redhat.com> <46DF17B6.9020907@ll.mit.edu> <46DF1A96.3010603@redhat.com> In-Reply-To: <46DF1A96.3010603@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact insight-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sourceware.org X-SW-Source: 2007-q3/txt/msg00052.txt.bz2 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 > >