From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17139 invoked by alias); 14 Dec 2009 18:27:50 -0000 Received: (qmail 17129 invoked by uid 22791); 14 Dec 2009 18:27:49 -0000 X-SWARE-Spam-Status: No, hits=-2.5 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; Mon, 14 Dec 2009 18:27:46 +0000 Received: from mailhost4.vmware.com (mailhost4.vmware.com [10.16.67.124]) by smtp-outbound-1.vmware.com (Postfix) with ESMTP id 918C113B37; Mon, 14 Dec 2009 10:27:45 -0800 (PST) Received: from [10.20.94.141] (msnyder-server.eng.vmware.com [10.20.94.141]) by mailhost4.vmware.com (Postfix) with ESMTP id 8A177C9A19; Mon, 14 Dec 2009 10:27:45 -0800 (PST) Message-ID: <4B26833C.4050803@vmware.com> Date: Mon, 14 Dec 2009 18:27:00 -0000 From: Michael Snyder User-Agent: Thunderbird 1.5.0.12 (X11/20090624) MIME-Version: 1.0 To: paawan oza CC: Hui Zhu , "gdb@sourceware.org" Subject: Re: porting reversible on arm/mips References: <816087.35180.qm@web112515.mail.gq1.yahoo.com> <4B218B30.4010501@vmware.com> <119734.20965.qm@web112506.mail.gq1.yahoo.com> <4B21B85F.1030502@vmware.com> <205443.37500.qm@web112520.mail.gq1.yahoo.com> <4B229428.7020400@vmware.com> <625230.40550.qm@web112506.mail.gq1.yahoo.com> <963513.51380.qm@web112512.mail.gq1.yahoo.com> In-Reply-To: <963513.51380.qm@web112512.mail.gq1.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-12/txt/msg00089.txt.bz2 paawan oza wrote: > another option what Micahel suggested... > "There's a nice separation in prec between architecture and OS/ABI. You could begin with the arm simulator that comes > built-in to gdb, and do the architecture part before tackling the Linux ABI part." > above also seems to be good too. for the time being I just concentrate on arch part and forget Linux ABI for the time being.. Seems to me you should be able to get quite far using this approach. Should be able to simulate and reverse-execute any piece of code that does not make system calls (directly or indirectly). Should be able to cover most of the user instruction set, especially if you are willing to write tests in assembler.