From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19040 invoked by alias); 4 Oct 2004 21:31:30 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 19029 invoked from network); 4 Oct 2004 21:31:29 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 4 Oct 2004 21:31:29 -0000 Received: from drow by nevyn.them.org with local (Exim 4.34 #1 (Debian)) id 1CEaQb-0007RS-Af; Mon, 04 Oct 2004 17:31:29 -0400 Date: Mon, 04 Oct 2004 21:31:00 -0000 From: Daniel Jacobowitz To: Felix Lee Cc: gdb-patches@sources.redhat.com Subject: Re: [patch] typo in gdb/testsuite/config/gdbserver.exp Message-ID: <20041004213129.GB30774@nevyn.them.org> Mail-Followup-To: Felix Lee , gdb-patches@sources.redhat.com References: <20041001073659.AB14A50106A@stray.canids> <20041004033025.GA19947@nevyn.them.org> <20041004084006.00F62502AB6@stray.canids> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041004084006.00F62502AB6@stray.canids> User-Agent: Mutt/1.5.5.1+cvs20040105i X-SW-Source: 2004-10/txt/msg00068.txt.bz2 On Mon, Oct 04, 2004 at 01:40:05AM -0700, Felix Lee wrote: > Daniel Jacobowitz : > > I seem to remember this breaking my local gdbserver setup, i.e. running > > gdbserver on localhost. It's entirely possible that that only happened > > because I've goofed my board files, though. I've learned a painful > > amount about writing DejaGNU board files in the last couple of months, > > so I'll try again... > > I just looked at that, it took me a few tries to get it to work. > this board file works for me: > > load_generic_config "gdbserver" > > unset_board_info isremote > set_board_info isremote 0 > > set_board_info compiler "[find_gcc]" > set_board_info gdb,do_reload_on_run 1 > set_board_info gdb,no_hardware_watchpoints 1 > set_board_info noargs 1 > set_board_info sockethost "localhost:" > set_board_info use_gdb_stub 1 But not very well. Here's a cleaned up version of mine... In any case, your patch to config/gdbserver.exp appears correct to me, and doesn't break my testing. Please check it in. # gdbserver running native. load_generic_config "gdbserver" set_board_info compiler "[find_gcc]" set_board_info gdb,do_reload_on_run 1 set_board_info gdb,no_hardware_watchpoints 1 set_board_info noargs 1 set_board_info sockethost "localhost:" set_board_info use_gdb_stub 1 process_multilib_options "" set_board_info gdb_protocol "remote" set_board_info gdb_server_prog "../gdbserver/gdbserver" set_board_info gdb,noinferiorio 1 proc ${board}_spawn { board cmd } { global board_info set baseboard [lindex [split $board "/"] 0] set board_info($baseboard,isremote) 0 set result [remote_spawn $board $cmd] set board_info($baseboard,isremote) 1 return $result } proc ${board}_download { board host dest } { return $host } -- Daniel Jacobowitz