From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 488 invoked by alias); 22 Nov 2005 12:42:42 -0000 Received: (qmail 477 invoked by uid 22791); 22 Nov 2005 12:42:39 -0000 X-Spam-Check-By: sourceware.org Received: from zproxy.gmail.com (HELO zproxy.gmail.com) (64.233.162.199) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 22 Nov 2005 12:42:35 +0000 Received: by zproxy.gmail.com with SMTP id n1so1116780nzf for ; Tue, 22 Nov 2005 04:42:33 -0800 (PST) Received: by 10.36.91.13 with SMTP id o13mr1401768nzb; Tue, 22 Nov 2005 04:42:32 -0800 (PST) Received: by 10.36.31.6 with HTTP; Tue, 22 Nov 2005 04:42:32 -0800 (PST) Message-ID: Date: Tue, 22 Nov 2005 12:42:00 -0000 From: Donny Kurniawan To: gdb@sources.redhat.com Subject: A lean/small GDB ? MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2005-11/txt/msg00475.txt.bz2 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-li= ke interface. Is this approach feasible/easy-to-do? Any comments/opinions are greatly appreciated. Thanks, Donny