public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb@sources.redhat.com
Subject: Re: libGDB and gdbserver questions
Date: Thu, 17 Nov 2005 03:58:00 -0000	[thread overview]
Message-ID: <20051117035843.GA3513@nevyn.them.org> (raw)
In-Reply-To: <dleor1$uk$1@sea.gmane.org>

On Wed, Nov 16, 2005 at 10:58:25AM +0300, Vladimir Prus wrote:
> Unfortunately, I don't know better way. Refactoring gdb to support several
> connections to remote targets and to add an explicit notion of "process"
> might be very hard.

Yes, I think it will be - however, it needs to get done eventually, I
think.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

  reply	other threads:[~2005-11-17  3:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-15 12:48 Donny Kurniawan
2005-11-15 14:18 ` Daniel Jacobowitz
2005-11-15 23:45   ` Donny Kurniawan
2005-11-16  0:40     ` Daniel Jacobowitz
2005-11-15 15:34 ` Vladimir Prus
2005-11-15 23:31   ` Donny Kurniawan
2005-11-16  8:01     ` Vladimir Prus
2005-11-17  3:58       ` Daniel Jacobowitz [this message]
2005-11-17 18:44         ` Stan Shebs
2005-11-21  8:01       ` Donny Kurniawan
2005-11-16  9:19   ` Konstantin Karganov
2005-11-21  8:04     ` Donny Kurniawan

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=20051117035843.GA3513@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=ghost@cs.msu.su \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).