From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27035 invoked by alias); 4 Aug 2009 18:26:38 -0000 Received: (qmail 27027 invoked by uid 22791); 4 Aug 2009 18:26:38 -0000 X-SWARE-Spam-Status: No, hits=0.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_JMF_BL,RCVD_IN_SORBS_WEB,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout4.012.net.il (HELO mtaout3.012.net.il) (84.95.2.10) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 04 Aug 2009 18:26:30 +0000 Received: from conversion-daemon.i_mtaout3.012.net.il by i_mtaout3.012.net.il (HyperSendmail v2004.12) id <0KNV001006NF0D00@i_mtaout3.012.net.il> for gdb-patches@sourceware.org; Tue, 04 Aug 2009 21:26:28 +0300 (IDT) Received: from HOME-C4E4A596F7 ([77.127.149.138]) by i_mtaout3.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0KNV008JE781K2S0@i_mtaout3.012.net.il>; Tue, 04 Aug 2009 21:26:26 +0300 (IDT) Date: Tue, 04 Aug 2009 18:26:00 -0000 From: Eli Zaretskii Subject: Re: [RFA/RFC] Add dump and load command to process record and replay In-reply-to: To: Hui Zhu Cc: msnyder@vmware.com, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83my6fo2pa.fsf@gnu.org> References: <4A749572.7030005@vmware.com> <4A75054C.9030304@vmware.com> <83ws5koinl.fsf@gnu.org> 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-08/txt/msg00060.txt.bz2 > From: Hui Zhu > Date: Tue, 4 Aug 2009 10:07:11 +0800 > Cc: msnyder@vmware.com, gdb-patches@sourceware.org > > > By the way, does it make sense to make the dump file portable, so that > > another host that supports debugging the same target could then use > > it? > > > > Yes, the dump file is portable like core file. Well, maybe I'm missing something important, but isn't the dump file a series of struct's defined as this: struct record_entry { struct record_entry *prev; struct record_entry *next; enum record_type type; union { /* reg */ struct record_reg_entry reg; /* mem */ struct record_mem_entry mem; } u; }; ? If so, then the dump file uses host's native pointers, so it is not portable to a different host. Right?