From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1785 invoked by alias); 20 May 2003 20:18:05 -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 1554 invoked from network); 20 May 2003 20:17:59 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.131) by sources.redhat.com with SMTP; 20 May 2003 20:17:59 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id B21322B2F; Tue, 20 May 2003 16:17:51 -0400 (EDT) Message-ID: <3ECA8D6F.4070001@redhat.com> Date: Tue, 20 May 2003 20:18:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Jacobowitz Cc: Kevin Buettner , cgd@broadcom.com, gdb-patches@sources.redhat.com Subject: Always remote: [WIP/RFC] MIPS registers overhaul References: <1030514220025.ZM10373@localhost.localdomain> <3EC461C1.1080104@redhat.com> <1030516230550.ZM12582@localhost.localdomain> <1030517004052.ZM13153@localhost.localdomain> <20030517205951.GA1507@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-05/txt/msg00367.txt.bz2 >> 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. Andrew