From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11643 invoked by alias); 26 Oct 2009 23:42:37 -0000 Received: (qmail 11633 invoked by uid 22791); 26 Oct 2009 23:42:35 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00 X-Spam-Check-By: sourceware.org Received: from etinternational-gw.customer.alter.net (HELO etinternational.com) (63.125.108.14) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 26 Oct 2009 23:42:30 +0000 Received: by etinternational.com (Postfix, from userid 5001) id EDEBBF0010; Mon, 26 Oct 2009 19:42:28 -0400 (EDT) Received: from pixie (pixie.xmen.eti [192.168.9.76]) by etinternational.com (Postfix) with ESMTP id A0F5F138033 for ; Mon, 26 Oct 2009 19:42:28 -0400 (EDT) Received: by pixie (Postfix, from userid 10026) id 57DC6A42A2; Mon, 26 Oct 2009 19:42:02 -0400 (EDT) Date: Mon, 26 Oct 2009 23:45:00 -0000 From: "Joshua D. Boyd" To: gdb@sourceware.org Subject: Extended a new target from target remote Message-ID: <20091026234202.GK1461@pixie> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.18 (2008-05-17) 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/msg00380.txt.bz2 I'm trying to work on extensions to GDB for a remote cluster. To do this I am creating an intermediate GDB server to talk to the compute hardware. 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. Thank you.