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: A lean/small GDB ?
Date: Tue, 22 Nov 2005 13:27:00 -0000	[thread overview]
Message-ID: <dlv634$pr7$1@sea.gmane.org> (raw)
In-Reply-To: <bba22c370511220442p302b4dd7xb19734937c2a1026@mail.gmail.com>

Donny Kurniawan wrote:

> Hello,
> 
> I think I need to re-think my approach to my scalability problem (i.e.
> debugging 1000 processes).... by solving it from a different angle.
> 
> I am thinking to reduce GDB (either through configure or removing some
> code, e.g. readline) so that it can be as lean/small as possible while
> retaining essential debug functionalities. Hopefully, the small size can
> help in the scalability.
> 
> I am thinking to remove the UI and make GDB like "libGDB" by putting
> API-like interface.

Isn't most of memory consumption of gdb due to large amount of debug info
that gcc helpfully puts into binaries? I doubt the problem is in code size
of gdb itself.

- Volodya


      reply	other threads:[~2005-11-22 13:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-22 12:42 Donny Kurniawan
2005-11-22 13:27 ` Vladimir Prus [this message]

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='dlv634$pr7$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