From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15513 invoked by alias); 5 Aug 2004 15:19:55 -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 15501 invoked from network); 5 Aug 2004 15:19:53 -0000 Received: from unknown (HELO miranda.se.axis.com) (212.209.10.220) by sourceware.org with SMTP; 5 Aug 2004 15:19:53 -0000 Received: from [10.84.130.1] (ironmaiden.se.axis.com [10.84.130.1]) by miranda.se.axis.com (8.12.9/8.12.9/Debian-5local0.1) with ESMTP id i75FJq2b010361 for ; Thu, 5 Aug 2004 17:19:52 +0200 Message-ID: <41125017.6030901@axis.com> Date: Thu, 05 Aug 2004 15:19:00 -0000 From: Orjan Friberg Organization: Axis Communications User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616 MIME-Version: 1.0 To: gdb-patches@sources.redhat.com Subject: Extending corefile.exp to handle remote targets Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-08/txt/msg00115.txt.bz2 I'm looking at testing the core dump functionality for CRIS (remote target, Linux-based). (The gcore functionality is not an option for a remote target, right?). I was thinking I should extend corefile.exp to work with a remote target, probably adding a register restoration check, and possibly even unifying it with gcore.exp - or is there a reason for the difference between the two? On the surface it looks like the only difference is how the core file is generated. Any hints or warnings before I proceed? -- Orjan Friberg Axis Communications