From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14604 invoked by alias); 12 Jun 2003 20:41:07 -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 12360 invoked from network); 12 Jun 2003 20:40:19 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 12 Jun 2003 20:40:19 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id h5CKeIH09425 for ; Thu, 12 Jun 2003 16:40:19 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h5CKdKI14746; Thu, 12 Jun 2003 16:39:20 -0400 Received: from localhost.localdomain (vpn50-31.rdu.redhat.com [172.16.50.31]) by pobox.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h5CKdJe25114; Thu, 12 Jun 2003 16:39:19 -0400 Received: (from kev@localhost) by localhost.localdomain (8.11.6/8.11.6) id h5CKcUN31055; Thu, 12 Jun 2003 13:38:30 -0700 Date: Thu, 12 Jun 2003 20:41:00 -0000 From: Kevin Buettner Message-Id: <1030612203829.ZM31054@localhost.localdomain> In-Reply-To: nak26 "RE: examining remote core dumps; MT support for attach;" (Jun 12, 4:17pm) References: <3EE90BFD@webmail.drexel.edu> To: nak26 , Daniel Jacobowitz Subject: Re: examining remote core dumps; MT support for attach; Cc: drow , gdb MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-06/txt/msg00221.txt.bz2 On Jun 12, 4:17pm, 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. > > Can anybody think of another way of doing that (not involving gdbserver)? Either copy the file to the host or use some sort of remote filesystem mount (e.g. NFS) to get at the core file. I have a feeling that this isn't exactly what you wanted to hear though... Kevin