From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id EAhtB3x6nmFjYAAAWB0awg (envelope-from ) for ; Wed, 24 Nov 2021 12:46:36 -0500 Received: by simark.ca (Postfix, from userid 112) id 1C64F1F0CE; Wed, 24 Nov 2021 12:46:36 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) 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=unavailable autolearn_force=no version=3.4.2 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 C321D1E940 for ; Wed, 24 Nov 2021 12:46:35 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 3A3343858435 for ; Wed, 24 Nov 2021 17:46:35 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3A3343858435 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1637775995; bh=Z3RHWD2lTrK+uJ6wB1OfBQVlrnvct4x8MBNv8LQPgAQ=; h=To:Date:In-Reply-To:References:Subject:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=I5t574lHRQIVY7YNjBJd4DuUsaM9QwinKsJZPxcYWUjZ+u4frw3y4e/eILLvHl5Np 9WhoeP8F+5ic7mT7uw4J3TwWg7lqAxaHP7drZM7PYYISisGrYckuUaw3FCPJKr0Zpt epZ6ogLU9NiyVjpuZZnEmiB+0/w/R3nwqtCP6BAI= Received: from mx0a-001b2d01.pphosted.com (mx0b-001b2d01.pphosted.com [148.163.158.5]) by sourceware.org (Postfix) with ESMTPS id 4052D3858C39 for ; Wed, 24 Nov 2021 17:46:17 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 4052D3858C39 Received: from pps.filterd (m0098413.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.1.2/8.16.1.2) with SMTP id 1AOGdtdH030802; Wed, 24 Nov 2021 17:46:15 GMT Received: from ppma02dal.us.ibm.com (a.bd.3ea9.ip4.static.sl-reverse.com [169.62.189.10]) by mx0b-001b2d01.pphosted.com with ESMTP id 3chq1amfqu-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 24 Nov 2021 17:46:15 +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 1AOHSio7008417; Wed, 24 Nov 2021 17:46:14 GMT Received: from b01cxnp22036.gho.pok.ibm.com (b01cxnp22036.gho.pok.ibm.com [9.57.198.26]) by ppma02dal.us.ibm.com with ESMTP id 3cerncj7my-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 24 Nov 2021 17:46:14 +0000 Received: from b01ledav005.gho.pok.ibm.com (b01ledav005.gho.pok.ibm.com [9.57.199.110]) by b01cxnp22036.gho.pok.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id 1AOHkDxj19727188 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 24 Nov 2021 17:46:13 GMT Received: from b01ledav005.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id D9A19AE062; Wed, 24 Nov 2021 17:46:13 +0000 (GMT) Received: from b01ledav005.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 2A5AEAE06F; Wed, 24 Nov 2021 17:46:13 +0000 (GMT) Received: from li-e362e14c-2378-11b2-a85c-87d605f3c641.ibm.com (unknown [9.211.121.24]) by b01ledav005.gho.pok.ibm.com (Postfix) with ESMTP; Wed, 24 Nov 2021 17:46:12 +0000 (GMT) Message-ID: To: John Baldwin , Simon Marchi , gdb-patches@sourceware.org Date: Wed, 24 Nov 2021 09:46:12 -0800 In-Reply-To: References: <3b8e450b9fb4f4bec97a6bfbe6e6a4816be780ee.camel@us.ibm.com> <4d51616392553dd308672f65f18909ebf0513fc0.camel@us.ibm.com> <95fbffc3-8d30-6e75-4f52-f6e534a13b20@FreeBSD.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 (3.28.5-16.el8) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-TM-AS-GCONF: 00 X-Proofpoint-GUID: m7U6yIRj91QHKNv71VoxtK1y-v6a5Rfm X-Proofpoint-ORIG-GUID: m7U6yIRj91QHKNv71VoxtK1y-v6a5Rfm Subject: RE: [PATCH] gdb fix for catch-syscall.exp X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.205,Aquarius:18.0.790,Hydra:6.0.425,FMLib:17.0.607.475 definitions=2021-11-24_06,2021-11-24_01,2020-04-07_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 impostorscore=0 phishscore=0 priorityscore=1501 spamscore=0 lowpriorityscore=0 bulkscore=0 mlxscore=0 adultscore=0 clxscore=1015 malwarescore=0 mlxlogscore=999 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2110150000 definitions=main-2111240094 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 Cc: Rogerio Alves Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" On Tue, 2021-11-23 at 14:34 -0800, John Baldwin wrote: > > > > On 11/23/21 12:34 PM, Simon Marchi wrote: > > > > The behavior on powerpc sounds like a bug to me, and adjusting the > > test > > like this patch did just covers it up. It doesn't make sense for > > that > > behavior to be different per arch, for the same OS. > > > > If you all agree that it's a bug, I would suggest reverting this > > patch > > and making a patch that kfails the test when on powerpc. And > > ideally, > > someone should dig to understand why we don't see the return on > > powerpc > > (and fix it), but I'm not here to tell what other people should > > work on > > :). > > I do think this is likely a kernel bug. In FreeBSD's case we report > a single > event for both the syscall exit and exec event (but set flags to > indicate that > both events are present.. in practice for GDB I think this means that > on > FreeBSD we only report the exec event. Not sure if it would be more > correct > to report two events to the core in that case.) I do think that a > given OS > should probably be consistent here across architectures. > So I sent out a preliminary patch for comments to revert the change and make it an xfail. I was looking to see where I should file a bug. The discussion has said it is a kernel bug. The Freebsd commit you pointed to is a distro fix from what I can see? So, is it really a linux kernel issue or something that the distros handle? I believe there is a ptrace code in glib see that interacts with the result from the kernel, is that where the fix should go to fix all arch? Anyway, it isn't clear to me at the moment which bugzilla a bug should be filed with. Thoughts? Carl