From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16870 invoked by alias); 12 Jun 2003 21:08:42 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 16831 invoked from network); 12 Jun 2003 21:08:42 -0000 Received: from unknown (HELO crack.them.org) (146.82.138.56) by sources.redhat.com with SMTP; 12 Jun 2003 21:08:42 -0000 Received: from dsl093-172-017.pit1.dsl.speakeasy.net ([66.93.172.17] helo=nevyn.them.org ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 19QZJz-0000ID-00; Thu, 12 Jun 2003 16:09:23 -0500 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 19QZJ9-0004Gx-00; Thu, 12 Jun 2003 17:08:31 -0400 Date: Thu, 12 Jun 2003 21:08:00 -0000 From: Daniel Jacobowitz To: nak26 Cc: drow , gdb Subject: Re: examining remote core dumps; MT support for attach; Message-ID: <20030612210831.GA16404@nevyn.them.org> Mail-Followup-To: nak26 , drow , gdb References: <3EE917EC@webmail.drexel.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3EE917EC@webmail.drexel.edu> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-06/txt/msg00224.txt.bz2 On Thu, Jun 12, 2003 at 04:59:55PM -0400, nak26 wrote: > >>> 1. Is it possible to examine a core file on a remote machine, in the > cases, > >> where fetching the core is undesirable due to the thinness of the pipe. > > > >This is not supported. > > How hard would it be to add support for that? I can give it a try, but would > need some guidance... I have no idea how you would do it. You'd have to transfer essentially the same info anyway. Or port gdbserver to have a "core file" target but I don't know how well that would work. > >> 2. Does the gdbserver that comes with gdb5.3 work with multithreaded apps, > or > >> it needs to be additionally patched? > > > >It should work. > > I saw a PREPARE_TO_PROCEED patch beeing mentioned in some of the posts. In > which cases it heeds to be applied? You'll probably never hit it unless you manually use the "thread" command to switch threads and then single-step the new thread. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer