From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id 5rk9L61me2KVlwUAWB0awg (envelope-from ) for ; Wed, 11 May 2022 03:33:01 -0400 Received: by simark.ca (Postfix, from userid 112) id B55C01E21F; Wed, 11 May 2022 03:33:01 -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=hfaCtI8V; 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,NICE_REPLY_A,RDNS_DYNAMIC, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from sourceware.org (ip-8-43-85-97.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 455BF1E01D for ; Wed, 11 May 2022 03:33:01 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id B272F384B402 for ; Wed, 11 May 2022 07:33:00 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B272F384B402 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1652254380; bh=mdOYHdvE/XsJ0CWoCPF+AgiQruWcEJY8T1hHR9GMaKw=; h=Date:Subject:To:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=hfaCtI8V18/GkT0DTj7f8dYKg/WvXAzcXcZYU8SnDvYi8c8ndENzGeV9SH3XAAiWR 5UkHJBx6/lM1ovqQ+HWsKKg+faO9YRYpqI9ITsD0slQwxCDFCaGEbOba/u/zrO4yEb hRf3TC2G1De/j969pg/KiEj1zimBa32gw2Ku+HAo= Received: from smtp-out2.suse.de (smtp-out2.suse.de [195.135.220.29]) by sourceware.org (Postfix) with ESMTPS id CC05D384F00F for ; Wed, 11 May 2022 07:22:55 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org CC05D384F00F Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id E952B1F8F7; Wed, 11 May 2022 07:22:54 +0000 (UTC) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id CE56213A76; Wed, 11 May 2022 07:22:54 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id uF0UMU5ke2IHTgAAMHmgww (envelope-from ); Wed, 11 May 2022 07:22:54 +0000 Message-ID: Date: Wed, 11 May 2022 09:22:54 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.0 Subject: Re: [PATCH][PATCH] Update syscalls/{ppc64,ppc}-linux.xml Content-Language: en-US To: Kevin Buettner References: <20220509154832.GA22531@delia> <20220510110243.74851f92@f35-zws-1> In-Reply-To: <20220510110243.74851f92@f35-zws-1> Content-Type: text/plain; charset=UTF-8; format=flowed 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: Tom de Vries via Gdb-patches Reply-To: Tom de Vries Cc: gdb-patches@sourceware.org Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" On 5/10/22 20:02, Kevin Buettner wrote: > 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... I've found here ( https://www.kernel.org/doc/Documentation/ABI/README ): ... Most interfaces (like syscalls) are expected to never change and always be available. ... So I suppose we don't need to worry about that. Thanks, - Tom