Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <ghost@cs.msu.su>
To: gdb@sources.redhat.com
Subject: Re: libGDB and gdbserver questions
Date: Tue, 15 Nov 2005 15:34:00 -0000	[thread overview]
Message-ID: <dlcu2c$ct1$1@sea.gmane.org> (raw)
In-Reply-To: <bba22c370511150448t1ab0102fi4f4e1e38979a512e@mail.gmail.com>

Donny Kurniawan wrote:

> 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'm not sure what you mean about "master UI controller". The biggest
scalability problem is that each gdb will load symbol table for your
program, and for real program that might take 100M of memory. Multiply that
by 1000 and you need 64-bit box.

However, it's not likely that you have 1000 different programs. If you have
two programs, and each one is run on 500 machines, you can start two copies
of gdb.

Then each copy of gdb would connect to a "redirector" you can write, that
will basically forward all packets to invididual instances of gdbserver.
But it will present those 500 instances as 500 threads, and gdb can work
with threads more or less fine.

As least, that what I plan to do for multi-program debugging.

- Volodya


  parent reply	other threads:[~2005-11-15 15:34 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 [this message]
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='dlcu2c$ct1$1@sea.gmane.org' \
    --to=ghost@cs.msu.su \
    --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