From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11501 invoked by alias); 18 Oct 2009 04:10:21 -0000 Received: (qmail 11485 invoked by uid 22791); 18 Oct 2009 04:10:20 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from smtp-outbound-1.vmware.com (HELO smtp-outbound-1.vmware.com) (65.115.85.69) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 18 Oct 2009 04:10:15 +0000 Received: from mailhost2.vmware.com (mailhost2.vmware.com [10.16.67.167]) by smtp-outbound-1.vmware.com (Postfix) with ESMTP id 6165D1303B; Sat, 17 Oct 2009 21:10:14 -0700 (PDT) Received: from [10.20.94.141] (msnyder-server.eng.vmware.com [10.20.94.141]) by mailhost2.vmware.com (Postfix) with ESMTP id 3F75A8E7CB; Sat, 17 Oct 2009 21:10:14 -0700 (PDT) Message-ID: <4ADA93C9.5040601@vmware.com> Date: Sun, 18 Oct 2009 04:10:00 -0000 From: Michael Snyder User-Agent: Thunderbird 1.5.0.12 (X11/20080411) MIME-Version: 1.0 To: Eli Zaretskii CC: "gdb-patches@sourceware.org" , "teawater@gmail.com" Subject: Re: [RFA, 3 of 3] save/restore process record, part 3 (save/restore) References: <4AD91D72.1030802@vmware.com> <831vl2ifui.fsf@gnu.org> <4ADA0EB3.60104@vmware.com> <83my3phjew.fsf@gnu.org> <4ADA4191.4060404@vmware.com> <83k4ytgxh5.fsf@gnu.org> In-Reply-To: <83k4ytgxh5.fsf@gnu.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-10/txt/msg00409.txt.bz2 Eli Zaretskii wrote: >> Date: Sat, 17 Oct 2009 15:13:37 -0700 >> From: Michael Snyder >> CC: "gdb-patches@sourceware.org" , >> "teawater@gmail.com" >> >>>> This is the same approach that is used by the "gcore" command. >>>> How does "gcore" work with go32, if at all? >>> It doesn't. DJGPP cannot generate core files. >> Well, save/restore depends on core files, so I guess >> it won't work in go32. > > DJGPP does not support core files created from a memory image of a > running process, but I don't see any reason why bfdcore_write won't > work for it. We don't just do bfdcore_write -- we actually create a core file from the memory image, and then add an extra segment to it for bfdcore_write to write into. The core file is an integral part of the execution log file. I forgot to post the accompanying changes to gcore.c with this patch. I'm just about to put them up now that Hui reminded me.