From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id kxZgJZnIemJbggUAWB0awg (envelope-from ) for ; Tue, 10 May 2022 16:18:33 -0400 Received: by simark.ca (Postfix, from userid 112) id 867BC1E21F; Tue, 10 May 2022 16:18:33 -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=gxgjYgws; 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 B09931E00D for ; Tue, 10 May 2022 16:18:31 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id D202D3898C69 for ; Tue, 10 May 2022 20:18:30 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D202D3898C69 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1652213910; bh=/W7Aa32KEC+UV2WYVuLubEE3LM8WT64gPKccuscA+ZM=; h=To:Date:In-Reply-To:References:Subject:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=gxgjYgws3yhsarwB9xWnDELPx+VsN7TnomWuhtxyhHKZs3/OGBwXSxtXMH670xXJV uNxQ/p6ChOB1x8xQATv2gR0LIlV/D+lM41dWCqPhwzL1mWVSCgXk24EXtM+6Fr7Fpg y4BjebteE8SC7fEb/B3ydQ3k4ecpMA8RND+59UFE= Received: from mx0a-001b2d01.pphosted.com (mx0a-001b2d01.pphosted.com [148.163.156.1]) by sourceware.org (Postfix) with ESMTPS id 11EBC3889813 for ; Tue, 10 May 2022 20:18:11 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 11EBC3889813 Received: from pps.filterd (m0098409.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.17.1.5/8.17.1.5) with ESMTP id 24AIMNSh003761; Tue, 10 May 2022 20:18:11 GMT Received: from ppma02dal.us.ibm.com (a.bd.3ea9.ip4.static.sl-reverse.com [169.62.189.10]) by mx0a-001b2d01.pphosted.com (PPS) with ESMTPS id 3fyw8vt4ce-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 10 May 2022 20:18:10 +0000 Received: from pps.filterd (ppma02dal.us.ibm.com [127.0.0.1]) by ppma02dal.us.ibm.com (8.16.1.2/8.16.1.2) with SMTP id 24AJwKgZ017946; Tue, 10 May 2022 20:18:10 GMT Received: from b01cxnp23033.gho.pok.ibm.com (b01cxnp23033.gho.pok.ibm.com [9.57.198.28]) by ppma02dal.us.ibm.com with ESMTP id 3fwgdad928-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 10 May 2022 20:18:10 +0000 Received: from b01ledav002.gho.pok.ibm.com (b01ledav002.gho.pok.ibm.com [9.57.199.107]) by b01cxnp23033.gho.pok.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id 24AKI97M37486876 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 10 May 2022 20:18:09 GMT Received: from b01ledav002.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 4F6C9124053; Tue, 10 May 2022 20:18:09 +0000 (GMT) Received: from b01ledav002.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id BBF11124052; Tue, 10 May 2022 20:18:08 +0000 (GMT) Received: from li-e362e14c-2378-11b2-a85c-87d605f3c641.ibm.com (unknown [9.211.152.172]) by b01ledav002.gho.pok.ibm.com (Postfix) with ESMTP; Tue, 10 May 2022 20:18:08 +0000 (GMT) Message-ID: <58d5119f8edf4cff1fb7b1d23d419553251f510d.camel@us.ibm.com> To: Tom de Vries , gdb-patches@sourceware.org Date: Tue, 10 May 2022 13:18:08 -0700 In-Reply-To: References: <20220509154832.GA22531@delia> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 (3.28.5-18.el8) X-TM-AS-GCONF: 00 X-Proofpoint-GUID: c6FvBvPz7jyX-IKBCB18OMomI4bTNBa8 X-Proofpoint-ORIG-GUID: c6FvBvPz7jyX-IKBCB18OMomI4bTNBa8 Content-Transfer-Encoding: 7bit X-Proofpoint-UnRewURL: 1 URL was un-rewritten MIME-Version: 1.0 Subject: RE: PATCH] Update syscalls/{ppc64,ppc}-linux.xml X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.205,Aquarius:18.0.858,Hydra:6.0.486,FMLib:17.11.64.514 definitions=2022-05-10_06,2022-05-10_01,2022-02-23_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 suspectscore=0 spamscore=0 lowpriorityscore=0 clxscore=1015 mlxscore=0 phishscore=0 impostorscore=0 mlxlogscore=886 bulkscore=0 adultscore=0 malwarescore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2202240000 definitions=main-2205100083 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: Carl Love via Gdb-patches Reply-To: Carl Love Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" Tom: On Tue, 2022-05-10 at 11:01 +0200, Tom de Vries via Gdb-patches > 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 have looked at the patch. I don't see anything that is an > issue/problem on PowerPC. Per Will's comment, to the extent that I can tell the syscall numbers are consistent with what I saw last year. I did note that you add syscall 359 getrandom. In other unrelated work on gdb record I get messages from gdb record about a couple of system calls that are not supported. Number 359 was one of them, I don't recall the other one off the top of my head. I had yet to run down what the name of the syscall is for 359 but hopefully it is getrandom. Not sure if your patch will fix the gdb record issue or not. I need to get back to digging into that more to find out. Carl