From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21545 invoked by alias); 10 May 2012 13:39:53 -0000 Received: (qmail 21527 invoked by uid 22791); 10 May 2012 13:39:52 -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; Thu, 10 May 2012 13:39:40 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q4ADdd3r018221 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 10 May 2012 09:39:39 -0400 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q4ADdbkZ020538 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 10 May 2012 09:39:38 -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: <87sjf9qecr.fsf@fleche.redhat.com> Date: Thu, 10 May 2012 13:39:00 -0000 In-Reply-To: (oza Pawandeep's message of "Thu, 10 May 2012 14:19:22 +0530") Message-ID: <87aa1gqhnq.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/msg00040.txt.bz2 Oza> The definition of system call record maps fine to x86. but arm Oza> syscall numbers are different. [partially] for e.g. on x86 sycall Oza> number for sys_epoll_create = 254 while on ARM it is 250. the more Oza> we go down on defined system calls the more the numbers are Oza> differing on ARM and we loose one to one trivial mapping. My understanding of the current design is that the ARM code would see the syscall 250, and have a mapping to turn that into gdb_sys_epoll_create (== 254). This can be done bidirectionally with two lookup tables. I suppose this could still not work in some scenarios. One question is whether these occur in practice or are merely theoretical. I don't really care about this API either way. With a solid justification it is fine to change it. Tom