From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14935 invoked by alias); 26 Oct 2009 23:45:14 -0000 Received: (qmail 14926 invoked by uid 22791); 26 Oct 2009 23:45:13 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 26 Oct 2009 23:45:08 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 1250F10ECF; Mon, 26 Oct 2009 23:45:07 +0000 (GMT) Received: from caradoc.them.org (209.195.188.212.nauticom.net [209.195.188.212]) by nan.false.org (Postfix) with ESMTP id D9D7810EC9; Mon, 26 Oct 2009 23:45:06 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1N2ZFJ-0001lO-JB; Mon, 26 Oct 2009 19:45:05 -0400 Date: Tue, 27 Oct 2009 00:12:00 -0000 From: Daniel Jacobowitz To: "Joshua D. Boyd" Cc: gdb@sourceware.org Subject: Re: Extended a new target from target remote Message-ID: <20091026234505.GA6521@caradoc.them.org> Mail-Followup-To: "Joshua D. Boyd" , gdb@sourceware.org References: <20091026234202.GK1461@pixie> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091026234202.GK1461@pixie> User-Agent: Mutt/1.5.20 (2009-06-14) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-10/txt/msg00381.txt.bz2 On Mon, Oct 26, 2009 at 07:42:02PM -0400, Joshua D. Boyd wrote: > Using the normal old GDB remote serial protocol works perfectly, but I'm > having trouble figuring out what to do on startup. When the user in GDB > types "target remote server:2345", after the connection is established > it would be handy to be able to send more information (such as the list > of nodes that the job is spread over) that had be set using set commands > before GDB starts trying to set "Hc-1" or reading the general registers. > Is there any hook to do this, without modifying remote.c? What I don't > want to have to do is create a new "target cluster" which would end up > mostly duplicating the code in remote.c. Can you use target extended-remote instead of target remote? That supports some process-level extensions - including connecting to a "not running" target. Then you can use GDB's normal attach or run command once you've set up whatever else you need. -- Daniel Jacobowitz CodeSourcery