From: "Joshua D. Boyd" <jdboyd@etinternational.com>
To: gdb@sourceware.org
Subject: Re: Extended a new target from target remote
Date: Tue, 27 Oct 2009 02:22:00 -0000 [thread overview]
Message-ID: <20091027001148.GL1461@pixie> (raw)
In-Reply-To: <20091026234505.GA6521@caradoc.them.org>
On Mon, Oct 26, 2009 at 07:45:05PM -0400, Daniel Jacobowitz wrote:
> 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.
What version of GDB was that added in? I should have mentioned that I
picked up hacking on the internal GDB 6.1, which I realize is extremely
old and I should have mentioned that up front, and is a little
embarassing.
next prev parent reply other threads:[~2009-10-27 0:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 23:45 Joshua D. Boyd
2009-10-27 0:12 ` Daniel Jacobowitz
2009-10-27 2:22 ` Joshua D. Boyd [this message]
2009-10-27 2:40 ` Daniel Jacobowitz
2009-10-27 7:17 ` Joshua D. Boyd
2009-10-27 15:04 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091027001148.GL1461@pixie \
--to=jdboyd@etinternational.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox