From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29751 invoked by alias); 15 Nov 2005 23:31:22 -0000 Received: (qmail 29522 invoked by uid 22791); 15 Nov 2005 23:31:15 -0000 Received: from zproxy.gmail.com (HELO zproxy.gmail.com) (64.233.162.198) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Tue, 15 Nov 2005 23:31:15 +0000 Received: by zproxy.gmail.com with SMTP id n1so1738377nzf for ; Tue, 15 Nov 2005 15:31:13 -0800 (PST) Received: by 10.37.18.77 with SMTP id v77mr5629133nzi; Tue, 15 Nov 2005 15:31:13 -0800 (PST) Received: by 10.36.31.6 with HTTP; Tue, 15 Nov 2005 15:31:13 -0800 (PST) Message-ID: Date: Tue, 15 Nov 2005 23:31:00 -0000 From: Donny Kurniawan To: Vladimir Prus Subject: Re: libGDB and gdbserver questions Cc: gdb@sources.redhat.com In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: 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/msg00302.txt.bz2 > > "master UI controller" (that controls GDBs). > > I'm not sure what you mean about "master UI controller". The biggest What I mean is the UI that is presented to the user, which manages breakpoints, execution, stepping etc. for multiple processes. > However, it's not likely that you have 1000 different programs. If you ha= ve It is only one single program being run for 1000 times (1000 processes). > two programs, and each one is run on 500 machines, you can start two copi= es > 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. Hmmm.... I'm curious with this approach. I did write a "proxy" redirector between gdbserver and gdb. But it only connects one gdbserver to one gdb. So basically with this approach (many gdbservers to one gdb), we present processes as threads to gdb? How about debugging multi-thread (!) program with many processes then? How do we present threads to gdb? It seems to me, this approach is a clean hack, but not the way it's supposed to be. Donny > > As least, that what I plan to do for multi-program debugging. > > - Volodya > >