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 8C6793858D32 for ; Thu, 30 Nov 2023 15:40:01 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 8C6793858D32 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=linux.ibm.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=linux.ibm.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 8C6793858D32 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=148.163.158.5 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1701358802; cv=none; b=axS3fbN1/8UNm6WYkAkz95xvNi+to4KzmoYSE3F9oynlxMHpA/npFKS3ctxst0C7Hhd7a6otaqDSsyUqjNab9c52omxE0wLA3Wrw8oozh5ud9gBSf3oxapTY/JbaAJPTEtK6r2Fgv4PjHwcv/VTXrbQ5k81oAf/wlhmVYyNYF/Y= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1701358802; c=relaxed/simple; bh=G5Bt95KAC6FdN1eSVkuR8EdA14YO97qkNavZZNyYvXM=; h=DKIM-Signature:Message-ID:Subject:From:To:Date:MIME-Version; b=xIpMQ5W1SboVYPwzq20rN5dv8iWPn1nIFxzvc/CXbxQcl4TxcXiL7ndzCVBuJegTSAsmRs/Ekhomt5s09f41I52jmqaVQJENkMY0XK+LcCyBHv/iJoMkTcq7hkCHSnnZWWp92UIPYZVlL04LsKQvw7+RPAGyzZFq/fJsousgrxQ= ARC-Authentication-Results: i=1; server2.sourceware.org Received: from pps.filterd (m0353725.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 3AUFTO5M022731; Thu, 30 Nov 2023 15:39:56 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ibm.com; h=message-id : subject : from : to : cc : date : in-reply-to : references : content-type : content-transfer-encoding : mime-version; s=pp1; bh=N/eeEZC/UT/9G9gPaES3Sr04xSbRullxq2aAWcA0jDQ=; b=fES7YVaIwTmW84HvmlGK9IdgB13O2JAGa/CG6+zsrjjAeVr2UlSM0rQqz06d8Qe2iHWt cvy0bai8kMeDttjFO6KGnCqAXCCF05tMESkdxu+2wFpw71bvNC97VWJ8tLClzkiwmiYW WseiOPLp8u+7cyfi9lGMfDRgLuKGgcLkxwJoghVWdbce944Fkhvxq2LSX4foCBTdkTHO JDdg6rOzi+5hY/UF0kuI6y2ou+rZA7bLINXmBFuefV1ykdzjWqxSiUeYqqV+/x3ZQvqC elgIugnViTWXACW4SSxtEAV9/PAOdOrudkWGRqyEarZu4biNH1rq2zDHhZ8okx0TYlF3 KA== Received: from pps.reinject (localhost [127.0.0.1]) by mx0a-001b2d01.pphosted.com (PPS) with ESMTPS id 3upw2u0b93-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 30 Nov 2023 15:39:56 +0000 Received: from m0353725.ppops.net (m0353725.ppops.net [127.0.0.1]) by pps.reinject (8.17.1.5/8.17.1.5) with ESMTP id 3AUFUWHR026451; Thu, 30 Nov 2023 15:39:55 GMT Received: from ppma23.wdc07v.mail.ibm.com (5d.69.3da9.ip4.static.sl-reverse.com [169.61.105.93]) by mx0a-001b2d01.pphosted.com (PPS) with ESMTPS id 3upw2u0b8r-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 30 Nov 2023 15:39:55 +0000 Received: from pps.filterd (ppma23.wdc07v.mail.ibm.com [127.0.0.1]) by ppma23.wdc07v.mail.ibm.com (8.17.1.19/8.17.1.19) with ESMTP id 3AUDnEjH008138; Thu, 30 Nov 2023 15:39:54 GMT Received: from smtprelay01.wdc07v.mail.ibm.com ([172.16.1.68]) by ppma23.wdc07v.mail.ibm.com (PPS) with ESMTPS id 3ukvrkxua7-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 30 Nov 2023 15:39:54 +0000 Received: from smtpav01.wdc07v.mail.ibm.com (smtpav01.wdc07v.mail.ibm.com [10.39.53.228]) by smtprelay01.wdc07v.mail.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id 3AUFdsG447055278 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 30 Nov 2023 15:39:54 GMT Received: from smtpav01.wdc07v.mail.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 6C09758063; Thu, 30 Nov 2023 15:39:54 +0000 (GMT) Received: from smtpav01.wdc07v.mail.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 206185804B; Thu, 30 Nov 2023 15:39:53 +0000 (GMT) Received: from wecm-9-67-78-200.wecm.ibm.com (unknown [9.67.78.200]) by smtpav01.wdc07v.mail.ibm.com (Postfix) with ESMTP; Thu, 30 Nov 2023 15:39:52 +0000 (GMT) Message-ID: <85a2f33d4ad12966dcb212e99e836175b69fddee.camel@linux.ibm.com> Subject: Re: [ PATCH 0/3] Fix GDB reverse execution behavior From: Carl Love To: Guinevere Larsen , Luis Machado , Ulrich Weigand , gdb-patches@sourceware.org Cc: Pedro Alves , Tom Tromey , Simon Marchi Date: Thu, 30 Nov 2023 07:39:52 -0800 In-Reply-To: <07f044da-94d5-bc7d-7d57-d83e9f179e59@redhat.com> References: <890101c23dd5fa60fcbf9d4b299cb2a533c260b7.camel@linux.ibm.com> <1e702d8f-e5b4-4719-b1e7-42210f350305@arm.com> <643afce1-ab9b-4e8b-bcbb-5738dc409a28@arm.com> <9e17008084c34f953f5318933436ec703250120a.camel@linux.ibm.com> <92a751d1-a4b9-4c21-821e-a1dc67207516@arm.com> <5483d77c72088a1e4d5dfed2eded2366643fc659.camel@linux.ibm.com> <07f044da-94d5-bc7d-7d57-d83e9f179e59@redhat.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 (3.28.5-22.el8) X-TM-AS-GCONF: 00 X-Proofpoint-ORIG-GUID: cgEiZJmlp8_W-F_QDj34yjvHCKpVoKDf X-Proofpoint-GUID: cDGCL1ur2igFCL7bdQ5NxF1BiO6JOLKB Content-Transfer-Encoding: 7bit X-Proofpoint-UnRewURL: 0 URL was un-rewritten MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.272,Aquarius:18.0.997,Hydra:6.0.619,FMLib:17.11.176.26 definitions=2023-11-30_14,2023-11-30_01,2023-05-22_02 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 clxscore=1015 suspectscore=0 mlxlogscore=275 phishscore=0 adultscore=0 priorityscore=1501 malwarescore=0 lowpriorityscore=0 mlxscore=0 spamscore=0 impostorscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2311060000 definitions=main-2311300112 X-Spam-Status: No, score=-3.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE 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: Guinevere: On Thu, 2023-11-30 at 12:36 +0100, Guinevere Larsen wrote: > On a side note, b4 didn't really like this series and I'm not sure > why. > My guess is that all 3 patches have the same email subject, but it > may > also be that I needed --3way when using git am. Either way, just > mentioning to gather knowledge on what b4 likes or doesn't like. I am not familiar with b4. I just did a Google search and found a description of it at: https://people.kernel.org/monsieuricon/introducing-b4-and-patch-attestation It seems to be a tool the maintainers can use for patch management. I will have to play around with it and see if I can figure out why b4 doesn't like the patch series. Is this something that people have started using? Carl