From: Donny Kurniawan <donny.kurniawan@gmail.com>
To: gdb@sources.redhat.com
Subject: libGDB and gdbserver questions
Date: Tue, 15 Nov 2005 12:48:00 -0000 [thread overview]
Message-ID: <bba22c370511150448t1ab0102fi4f4e1e38979a512e@mail.gmail.com> (raw)
Hello,
I am trying to write a remote debugger for multiple processes. As far
as I know, most of the parallel debuggers (that use GDB as the
backend), use multiple instances of GDB, where each instance controls
one process.
The problem is: I want to be able to handle a lot of processes (1000
processes is the minimum), clearly having 1000 instances of GDB
controlling 1000 processes is not very scalable, and it will choke the
"master UI controller" (that controls GDBs).
I've been thinking about 2 solutions:
(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?
(2) libGDB
Actually, what's the state of libGDB (v. 2)? Not much docs that I can
find, only http://sources.redhat.com/gdb/papers/libgdb2/ and the
source code. Is it going to be more suitable to address the problem
mentioned above.
Any pointers/directions/opinions are appreciated...
I tried googling and looking at the mailing list, but the minimum
requirement to be able to handle 1000 procs makes the problem unusual.
Thank you,
Donny
next reply other threads:[~2005-11-15 12:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 12:48 Donny Kurniawan [this message]
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
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=bba22c370511150448t1ab0102fi4f4e1e38979a512e@mail.gmail.com \
--to=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).