From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id qQRvK+WoemJzewUAWB0awg (envelope-from ) for ; Tue, 10 May 2022 14:03:17 -0400 Received: by simark.ca (Postfix, from userid 112) id A0A591E21F; Tue, 10 May 2022 14:03:17 -0400 (EDT) Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=vaRSKIkw; dkim-atps=neutral X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-3.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 33C7A1E143 for ; Tue, 10 May 2022 14:03:17 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 56FBF3857825 for ; Tue, 10 May 2022 18:03:16 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 56FBF3857825 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1652205796; bh=DowZF5kGjsAdtr5EC7McNcCRkjId9zkKQqmQSRZnQMs=; h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=vaRSKIkwqdXxy6Mcz+AbsHXNxFhec2OEuyLuGJOJ7mQlEeHpNiyyiQRDpa6tWz838 oge2X2UqR9RtYTPiB1lEePpA/o6sk2qrC6+Bs9AKdojqaYp8VMspPkKWFhdcB1fG6j Hbw47D+EFwgBCo1/I0dqtBFdifVS2HKDp/i6PeNM= Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id 09B653858C56 for ; Tue, 10 May 2022 18:02:57 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 09B653858C56 Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-639-kEpbQFq3MXO9sDU1xL2vuQ-1; Tue, 10 May 2022 14:02:45 -0400 X-MC-Unique: kEpbQFq3MXO9sDU1xL2vuQ-1 Received: from smtp.corp.redhat.com (int-mx10.intmail.prod.int.rdu2.redhat.com [10.11.54.10]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 08D41101AA46; Tue, 10 May 2022 18:02:45 +0000 (UTC) Received: from f35-zws-1 (unknown [10.2.17.65]) by smtp.corp.redhat.com (Postfix) with ESMTPS id BA95D402D8F; Tue, 10 May 2022 18:02:44 +0000 (UTC) Date: Tue, 10 May 2022 11:02:43 -0700 To: Tom de Vries Subject: Re: [PATCH][PATCH] Update syscalls/{ppc64,ppc}-linux.xml Message-ID: <20220510110243.74851f92@f35-zws-1> In-Reply-To: References: <20220509154832.GA22531@delia> Organization: Red Hat MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.85 on 10.11.54.10 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Kevin Buettner via Gdb-patches Reply-To: Kevin Buettner Cc: gdb-patches@sourceware.org Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" On Tue, 10 May 2022 11:01:27 +0200 Tom de Vries wrote: > On 5/9/22 17:48, Tom de Vries wrote: > > Hi, > > > > Regenerate syscalls/{ppc64,ppc}-linux.xml on a system with 5.14 kernel. > > > > Note btw that it does not only add, but also renumbers, f.i.: > > ... > > - > > + > > ... > > > > Currently testing. > > > > Here's a v2, with a gdb.base/catch-syscall.exp test-case fix included. > > Testing on ppc64le revealed: > ... > (gdb) catch syscall 286^M > Catchpoint 2 (syscall 'openat' [286])^M > (gdb) FAIL: gdb.base/catch-syscall.exp: multiple targets: insert catch > syscall on syscall 286\ > -- unlinkat on powerpc:common64 > ... > > FWIW, I've wrote a patch that exposes the same problem on x86_64-linux ( > https://sourceware.org/pipermail/gdb-patches/2022-May/188881.html ). > > Any comments? I don't have a problem with your patch, which (mostly) updates system call numbers. What I am wondering about is how often they change? Also, what happens when a GDB with some set of syscall numbers is used with a kernel which uses different numbers? (Nothing good, I'd guess.) I'm just wondering if there's a better way to do things... Kevin