From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17706 invoked by alias); 16 May 2012 14:57:30 -0000 Received: (qmail 17687 invoked by uid 22791); 16 May 2012 14:57:29 -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, 16 May 2012 14:57:17 +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 q4GEurGo018068 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 16 May 2012 10:56:53 -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 q4GEupo8028076 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 16 May 2012 10:56:52 -0400 From: Tom Tromey To: oza Pawandeep Cc: Joel Brobecker , gdb@sourceware.org, gdb-patches@sourceware.org Subject: Re: [design change] record-replay linux ABI level References: <87sjf9qecr.fsf@fleche.redhat.com> <87aa1gqhnq.fsf@fleche.redhat.com> <20120514145650.GF10253@adacore.com> <87havhtmzy.fsf@fleche.redhat.com> Date: Wed, 16 May 2012 14:57:00 -0000 In-Reply-To: (oza Pawandeep's message of "Wed, 16 May 2012 16:18:05 +0530") Message-ID: <874nrgrx70.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/msg00074.txt.bz2 >>>>> "oza" == 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. That is, have a single generic enum; then map the system-specific numbers to this enum. The difference is that the mappings would be generated from the XML files. oza> define as follows oza> enum gdb_syscall oza> { oza> /* i386 related syscalls */ oza> /* ARM related syscalls */ oza> /* MIPS related syscalls */ oza> so on.. oza> } Yeah, I don't like this much. Tom