Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: David Taylor <dtaylor@emc.com>
Cc: Yao Qi <yao@codesourcery.com>,
	"gdb\@sourceware.org" <gdb@sourceware.org>
Subject: Re: add-inferior / clone-inferior
Date: Tue, 21 May 2013 13:52:00 -0000	[thread overview]
Message-ID: <87li78l9t7.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20412.1369142110@usendtaylorx2l> (David Taylor's message of	"Tue, 21 May 2013 09:15:10 -0400")

>>>>> "David" == David Taylor <dtaylor@emc.com> writes:

David> I want to have separate sockets at GDB's end.  I do not want to have a
David> "meta stub" (not really a good name, but nothing better quickly comes to
David> mind) on the local box that managers tcp connections and peeks into the
David> packets to determine when to set up or break down a new tcp connection
David> and where to send the packets.

I've been calling that a "federating gdbserver".
It federates multiple instances into a single server.

David> THat approach is UGLY.

It has one advantage -- you can link them together hierarchically, so
gdb can talk to more remote servers than it has available file
descriptors.


Anyway, I certainly want gdb to be multi-target-capable.  I think others
do too.  It just requires someone to do the work.

Tom


  reply	other threads:[~2013-05-21 13:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-20 14:43 David Taylor
2013-05-20 15:06 ` Luis Machado
2013-05-20 15:46   ` David Taylor
2013-05-20 15:52     ` Luis Machado
2013-05-21  1:01 ` Yao Qi
2013-05-21 13:15   ` David Taylor
2013-05-21 13:52     ` Tom Tromey [this message]
2013-05-21 14:35       ` David Taylor
2013-05-21 15:46 ` Tom Tromey
2013-05-22 14:47   ` Tom Tromey
2013-05-22 18:21     ` David Taylor
2013-05-22 18:50       ` Tom Tromey
2013-05-22 19:42         ` David Taylor
2013-05-22 20:21           ` Tom Tromey
2013-06-24 20:50   ` Tom Tromey

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=87li78l9t7.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=dtaylor@emc.com \
    --cc=gdb@sourceware.org \
    --cc=yao@codesourcery.com \
    /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