From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10191 invoked by alias); 9 May 2012 20:39:04 -0000 Received: (qmail 10115 invoked by uid 22791); 9 May 2012 20:39:02 -0000 X-SWARE-Spam-Status: No, hits=-6.4 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 09 May 2012 20:38:47 +0000 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q49KcjHb011135 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 9 May 2012 16:38:45 -0400 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q49Kcixd025331 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 9 May 2012 16:38:44 -0400 From: Tom Tromey To: oza Pawandeep Cc: gdb@sourceware.org, gdb-patches@sourceware.org Subject: Re: [design change] record-replay linux ABI level References: Date: Wed, 09 May 2012 20:39:00 -0000 In-Reply-To: (oza Pawandeep's message of "Wed, 9 May 2012 14:46:21 +0530") Message-ID: <87sjf9qecr.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.95 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain 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: 2012-05/txt/msg00035.txt.bz2 >>>>> "oza" == oza Pawandeep writes: oza> currently linux-record.h is having defination of oza> enum gdb_syscall {...} which seems generic one, but infact it only oza> addresses i386 arch. Based on reading the header, it seems to me that the idea is that this enum is intended to be generic, and that each target must provide its own mapping from the local syscalls to these. oza> I am thinking of moving all the definition to i386 specific files oza> (assuming there is no generic way to address all the systemcalls on oza> all arch). It seems to me that most syscalls could perhaps be shared, but maybe some architectures will require additions to the enum. I'm not sure, though. Could you say in more detail what problem you ran into? Tom