This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Extended a new target from target remote
- From: Daniel Jacobowitz <drow at false dot org>
- To: "Joshua D. Boyd" <jdboyd at etinternational dot com>
- Cc: gdb at sourceware dot org
- Date: Mon, 26 Oct 2009 19:45:05 -0400
- Subject: Re: Extended a new target from target remote
- References: <20091026234202.GK1461@pixie>
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