From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx0b-001b2d01.pphosted.com (mx0b-001b2d01.pphosted.com [148.163.158.5]) by sourceware.org (Postfix) with ESMTPS id 84A823858D37 for ; Fri, 13 Jan 2023 16:43:38 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 84A823858D37 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=us.ibm.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=us.ibm.com Received: from pps.filterd (m0098417.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 30DGQuIY025079 for ; Fri, 13 Jan 2023 16:43:38 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ibm.com; h=message-id : from : to : cc : date : in-reply-to : references : content-type : mime-version : content-transfer-encoding : subject; s=pp1; bh=/jhdm037OAMCek1f6gSWYKMm1CPAGsMCXwqyQnmz3C8=; b=X9MdA6YcFyXkcNtrKYF7zXUCK++Klo7ByUIenkqLZcs2AboENyoS/nJMTjmcxGjb0v+6 nSP7u4PpQOGmYgmsZdVi/lKpudeFeFp8DdGW88V9Hj52x6/oxToZRF4SDn0PHh4suUj2 lvmRVskZxFP24Rx9r0/oiDbx/YiZC0KhCTMyYwGEhjG2GlcnMenewUcAAV++CUrXQIn4 2IaCwQzg8wnZsLzDAC5I8cZe/Mq/RhttWylpuvcycA4NW5HY4zO0Y8iA9IdfvjyN9Dzj 6Z6BftQ4lVBauGJBIiw20wNOv0fO1PnESjijorIduVBm9M0cmbIRR2ABANafSxqs/b4s wQ== Received: from pps.reinject (localhost [127.0.0.1]) by mx0a-001b2d01.pphosted.com (PPS) with ESMTPS id 3n3att8eqk-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Fri, 13 Jan 2023 16:43:37 +0000 Received: from m0098417.ppops.net (m0098417.ppops.net [127.0.0.1]) by pps.reinject (8.17.1.5/8.17.1.5) with ESMTP id 30DGRHno025969 for ; Fri, 13 Jan 2023 16:43:37 GMT Received: from ppma03wdc.us.ibm.com (ba.79.3fa9.ip4.static.sl-reverse.com [169.63.121.186]) by mx0a-001b2d01.pphosted.com (PPS) with ESMTPS id 3n3att8eqa-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 13 Jan 2023 16:43:37 +0000 Received: from pps.filterd (ppma03wdc.us.ibm.com [127.0.0.1]) by ppma03wdc.us.ibm.com (8.17.1.19/8.17.1.19) with ESMTP id 30DGOST6013197; Fri, 13 Jan 2023 16:43:36 GMT Received: from smtprelay07.wdc07v.mail.ibm.com ([9.208.129.116]) by ppma03wdc.us.ibm.com (PPS) with ESMTPS id 3n1k940v72-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 13 Jan 2023 16:43:36 +0000 Received: from smtpav04.wdc07v.mail.ibm.com (smtpav04.wdc07v.mail.ibm.com [10.39.53.231]) by smtprelay07.wdc07v.mail.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id 30DGhZk38847958 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 13 Jan 2023 16:43:35 GMT Received: from smtpav04.wdc07v.mail.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id A8D4358050; Fri, 13 Jan 2023 16:43:35 +0000 (GMT) Received: from smtpav04.wdc07v.mail.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 1126C58045; Fri, 13 Jan 2023 16:43:35 +0000 (GMT) Received: from li-e362e14c-2378-11b2-a85c-87d605f3c641.ibm.com (unknown [9.163.12.142]) by smtpav04.wdc07v.mail.ibm.com (Postfix) with ESMTP; Fri, 13 Jan 2023 16:43:34 +0000 (GMT) Message-ID: <41aed5ea42d8888d9bc40c5102088e89e389937c.camel@us.ibm.com> From: Carl Love To: Bruno Larsen , Ulrich Weigand , "will_schmidt@vnet.ibm.com" , gdb-patches@sourceware.org Cc: cel@us.ibm.com Date: Fri, 13 Jan 2023 08:43:34 -0800 In-Reply-To: References: <5b50668cbe882c57b8c0e9dcf5be0a253713c4c6.camel@us.ibm.com> <51c4bfc82ac72e475e10577dc60e4d75fa48767e.camel@de.ibm.com> <3ea97a8aa9cccb39299adde682f92055d1986ab3.camel@us.ibm.com> <53878e37c6e57de1d04d9c9960c5d0a74324ee6e.camel@us.ibm.com> <50474aa92ba82eff05cdc8f49001eae56be29670.camel@us.ibm.com> <89331c26795e3f7743e1e068dce43b3c2dd53008.camel@us.ibm.com> <071f24ecf9b3a2bbbe8fee7db77492eb55c5f3ff.camel@us.ibm.com> <1d9b21914354bef6a290ac30673741e722e11757.camel@de.ibm.com> <3e3c9c40f07ab01c79fe10915e76ffa187c42ad9.camel@us.ibm.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 (3.28.5-18.el8) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-TM-AS-GCONF: 00 X-Proofpoint-GUID: LiuBmxCrDjXHGFHNEnk2chugUdf4O83c X-Proofpoint-ORIG-GUID: Ct0MmXokP4ENWckOmJBmxmIOmAVaL99o Subject: RE: [PATCH 1/2] fix for gdb.reverse/finish-precsave.exp and gdb.reverse/finish-reverse.exp X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.219,Aquarius:18.0.923,Hydra:6.0.562,FMLib:17.11.122.1 definitions=2023-01-13_07,2023-01-13_02,2022-06-22_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 mlxlogscore=751 impostorscore=0 suspectscore=0 phishscore=0 clxscore=1015 malwarescore=0 spamscore=0 bulkscore=0 mlxscore=0 adultscore=0 lowpriorityscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2212070000 definitions=main-2301130110 X-Spam-Status: No, score=-5.4 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Bruno: On Fri, 2023-01-13 at 14:33 +0100, Bruno Larsen wrote: > > +# This file is part of the GDB testsuite. It tests reverse > > stepping. > > +# Lots of code borrowed from "step-test.exp". > > + > > +# The reverse finish command should return from a function and > > stop on > > +# the first instruction of the source line where the function call > > is made. > > +# Specifically, the behavior should match doing a reverse next > > from the > > +# first instruction in the function. GDB should only take one > > reverse step > > +# or next statement to reach the previous source code line. > > + > > +# This testcase verifies the reverse-finish command stops at the > > first > > +# instruction in the source code line where the function was > > called. There > > +# are two scenarios that must be checked: > > +# 1) gdb is at the entry point instruction for the function > > +# 2) gdb is in the body of the function. > > While testing locally, I ran into a bug with reverse finish at the > epilogue of the function, that your patch also fixed. It would be > nice > if the test extended that. And since the bug was that GDB stopped > responding and even ctrl+c did nothing, I would suggest adding it as > the > last test. I haven't run into the issue that mentioned about GDB not responding in the epilogue. I will have to go play with that to see if I can reproduce it. If you have any specific instructions on how you ran into it that would be interesting and helpful. I have read thru the other comments and will work on them and update you on those fixes later. Thanks for the feedback. Carl