public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Donny Kurniawan <donny.kurniawan@gmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: libGDB and gdbserver questions
Date: Tue, 15 Nov 2005 14:18:00 -0000	[thread overview]
Message-ID: <20051115141835.GA21125@nevyn.them.org> (raw)
In-Reply-To: <bba22c370511150448t1ab0102fi4f4e1e38979a512e@mail.gmail.com>

On Tue, Nov 15, 2005 at 11:48:03PM +1100, Donny Kurniawan wrote:
> (1) gdbserver
> Since one gdbserver requires one instance of GDB, my plan is to use
> gdbserver as the low-level debugging engine and extend GDB to be able
> to handle multiple connections from gdbserver (correct me if I'm being
> too simplistic). Is there a support for it in GDB?

This isn't the problem.  Extending the GDB native backend to handle
multiple processes wouldn't be hard; it's extending the user interface
and process control and breakpoint management and shared library
support and so on to handle multiple processes that is difficult.

GDB simply doesn't support what you want to do.  Yet.

> (2) libGDB
> Actually, what's the state of libGDB (v. 2)? Not much docs that I can

Nothing has happened on this front in a long long time.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

  reply	other threads:[~2005-11-15 14:18 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 [this message]
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
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=20051115141835.GA21125@nevyn.them.org \
    --to=drow@false.org \
    --cc=donny.kurniawan@gmail.com \
    --cc=gdb@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).