From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18133 invoked by alias); 20 May 2003 20:26:01 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 18019 invoked from network); 20 May 2003 20:25:55 -0000 Received: from unknown (HELO crack.them.org) (146.82.138.56) by sources.redhat.com with SMTP; 20 May 2003 20:25:55 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 19IDgn-0006mD-00; Tue, 20 May 2003 15:26:25 -0500 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 19IDg1-0004Rk-00; Tue, 20 May 2003 16:25:37 -0400 Date: Tue, 20 May 2003 20:26:00 -0000 From: Daniel Jacobowitz To: Andrew Cagney Cc: Kevin Buettner , cgd@broadcom.com, gdb-patches@sources.redhat.com Subject: Re: Always remote: [WIP/RFC] MIPS registers overhaul Message-ID: <20030520202536.GA17055@nevyn.them.org> Mail-Followup-To: Andrew Cagney , Kevin Buettner , cgd@broadcom.com, gdb-patches@sources.redhat.com References: <1030516230550.ZM12582@localhost.localdomain> <1030517004052.ZM13153@localhost.localdomain> <20030517205951.GA1507@nevyn.them.org> <3ECA8D6F.4070001@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3ECA8D6F.4070001@redhat.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-05/txt/msg00369.txt.bz2 On Tue, May 20, 2003 at 04:17:51PM -0400, Andrew Cagney wrote: > > >>Another one (and it's a doozie) is that thread debugging won't work > >>due to the ABI specific libthread_db.so library that's dlopen'd by > >>RDA. A native GDB (assuming that we did the necessary work to port it > >>to mips64-linux) would have the same problem. We've kicked around > >>some ideas for fixing this problem in the past. The only idea that > >>I've found compelling is from Alex Oliva (and perhaps others) who > >>suggested that it may be best for a "native" gdb to spawn an > >>ABI-specific rda or gdbserver and connect to it automatically. > > > > > >TBH, I'd rather like to see us develop an extended and more extensible > >remote protocol (on any number of people's TODO lists already!) and do > >_all_ native debugging this way. > > FYI, one of the long ago identified scalability problems (by HP) with > GDB was all the memory moving/sucking that it did. HP were looking for > ways to MMAP memory and avoiding doing all the copies. Having GDB suck > memory through a straw would be a odds with that. > > Note, I'm talking here about megabytes of memory - people try to use the > debuger to draw plots of their fortran arrays. Definitely something to keep in mind... but I think not necessarily in conflict. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer