From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23103 invoked by alias); 5 Jun 2012 09:16:30 -0000 Received: (qmail 23085 invoked by uid 22791); 5 Jun 2012 09:16:29 -0000 X-SWARE-Spam-Status: No, hits=-4.7 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mail-lpp01m010-f41.google.com (HELO mail-lpp01m010-f41.google.com) (209.85.215.41) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 05 Jun 2012 09:16:17 +0000 Received: by lahi5 with SMTP id i5so4320794lah.0 for ; Tue, 05 Jun 2012 02:16:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.112.43.37 with SMTP id t5mr7812125lbl.89.1338887775349; Tue, 05 Jun 2012 02:16:15 -0700 (PDT) Received: by 10.152.24.40 with HTTP; Tue, 5 Jun 2012 02:16:15 -0700 (PDT) In-Reply-To: <874nrgrx70.fsf@fleche.redhat.com> References: <87sjf9qecr.fsf@fleche.redhat.com> <87aa1gqhnq.fsf@fleche.redhat.com> <20120514145650.GF10253@adacore.com> <87havhtmzy.fsf@fleche.redhat.com> <874nrgrx70.fsf@fleche.redhat.com> Date: Tue, 05 Jun 2012 09:16:00 -0000 Message-ID: Subject: Re: [design change] record-replay linux ABI level From: oza Pawandeep To: Tom Tromey Cc: Joel Brobecker , gdb@sourceware.org, gdb-patches@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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: 2012-06/txt/msg00026.txt.bz2 I have gone through some of the xml stuffs already done. under gdb/syscalls/arch_linux.xml files exist. which is currently not used for record-purpose. there are 2 ways we could go ahead now: 1) use the above file for recording purpose too and define new arm-linux.xml for arm specific syscalls. 2) or we decide to keep only one combined xml files for record-replay future for all arch. PS: syscall code is almost done now, it supports 242 syscalls [till gdb_sys_sched_getaffinity =3D 242] (xml stuff is pending) Regards, Oza. On Wed, May 16, 2012 at 8:26 PM, Tom Tromey wrote: >>>>>> "oza" =3D=3D oza Pawandeep writes: > > oza> b) I am not much familiar with xml generated C files, and where to > oza> change in gdb, but with that, will the record_linux_system_call be > oza> able to incorporate all conflicting syscall numbers in that case ? > > The idea is to extend the current approach. =A0That is, have a single > generic enum; then map the system-specific numbers to this enum. =A0The > difference is that the mappings would be generated from the XML files. > > oza> define as follows > oza> enum gdb_syscall > oza> { > oza> =A0 =A0 =A0 =A0 =A0 =A0/* i386 related syscalls */ > oza> =A0 =A0 =A0 =A0 =A0 =A0/* ARM related syscalls */ > oza> =A0 =A0 =A0 =A0 =A0 =A0/* MIPS related syscalls */ > oza> =A0 =A0 =A0 =A0 =A0 =A0so on.. > oza> } > > Yeah, I don't like this much. > > Tom