From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id CXmbLo7tYGrZ9yUAWB0awg (envelope-from ) for ; Wed, 22 Jul 2026 12:19:26 -0400 Authentication-Results: simark.ca; dkim=pass (2048-bit key; unprotected) header.d=yahoo.de header.i=@yahoo.de header.a=rsa-sha256 header.s=s2048 header.b=CgpkRX4+; dkim-atps=neutral Received: by simark.ca (Postfix, from userid 112) id AA38A1E09E; Wed, 22 Jul 2026 12:19:26 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-25) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-5.4 required=5.0 tests=ARC_SIGNED,ARC_VALID,BAYES_00, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED autolearn=ham autolearn_force=no version=4.0.1 Received: from vm01.sourceware.org (vm01.sourceware.org [38.145.34.32]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id AF05B1E033 for ; Wed, 22 Jul 2026 12:19:25 -0400 (EDT) Received: from vm01.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 0CCFF4BA2E25 for ; Wed, 22 Jul 2026 16:19:25 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0CCFF4BA2E25 Authentication-Results: sourceware.org; dkim=pass (2048-bit key, unprotected) header.d=yahoo.de header.i=@yahoo.de header.a=rsa-sha256 header.s=s2048 header.b=CgpkRX4+ Received: from sonic304-22.consmr.mail.ir2.yahoo.com (sonic304-22.consmr.mail.ir2.yahoo.com [77.238.179.147]) by sourceware.org (Postfix) with ESMTPS id A58994BA2E04 for ; Wed, 22 Jul 2026 16:18:58 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org A58994BA2E04 Authentication-Results: sourceware.org; dmarc=pass (p=reject dis=none) header.from=yahoo.de Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=yahoo.de ARC-Filter: OpenARC Filter v1.0.0 sourceware.org A58994BA2E04 Authentication-Results: sourceware.org; arc=none smtp.remote-ip=77.238.179.147 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1784737138; cv=none; b=td/wIumh53QXyp8hIxz0ixgvHs7LBMRIDnBDvwHyVnAtgLzOUXUzc6b0Gy/77JUHvfJhg0tmsBvTL7fZvptsjBP6YXb0lPk2xWDBWVKFqb0S9kpFPwB39eaYPggiIwaDi4GQrlc+Sli1dVxFPQ04rVAxi+WfCYuTx4Blj34BOa4= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1784737138; c=relaxed/simple; bh=fS8NkM8WHS6uwmMVP8CXIhzaQkFM6la1LfsyG/y9KDs=; h=DKIM-Signature:Date:From:To:Message-ID:Subject:MIME-Version; b=UeCq9UMWOgI7qNvvFfKLbVmQwY4iHK09GpC038f+BLI4ABtRvvX7S8g+igmWxSQKMU36bwUK+6sFAvMTPQzW4Yj85NQjeBJea/DHnuCtHDrMu3kv51YR7C0OZazjGFSIxFJQN2moS7HA5r1Zr/mKdV6X9VYrYZEjOL+EBFwCxgE= ARC-Authentication-Results: i=1; sourceware.org; dkim=pass (2048-bit key, unprotected) header.d=yahoo.de header.i=@yahoo.de header.a=rsa-sha256 header.s=s2048 header.b=CgpkRX4+ DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A58994BA2E04 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.de; s=s2048; t=1784737136; bh=fS8NkM8WHS6uwmMVP8CXIhzaQkFM6la1LfsyG/y9KDs=; h=Date:From:To:References:Subject:From:Subject:Reply-To; b=CgpkRX4+dwfxmki0vEA/Gjt8N7qLSd5y9mXTMja29zIKg7stmJO1gL5Dsdcf0cTZ5fgS2IbwXUzCiXAJKTYMcMCwOTlCdZPByc01lc4ThIEWsquJy2MRGkdtQr91bBEUWfZRvbPYsJ9Al+OptKQLSOiaI1Mz4seVAbZmKXOjPNE4k8OP+xw8seJtCbVs2TMiijW+NfS1FnSRbQUnLls6v6juyhLVkbQ1VBmLsWPZq4cWx6XjQDwb6/4YJxFozQ0u/ainFEYBbsYgNFDVoEZiTebMfKoe47PdiopDqseGhbDwg+YPhFr8xhoCyZqj+TFTob74/8aOwfBAEzpYF4fbcQ== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1784737136; bh=4hidg9VKiXlVMofecNXEduzP9KD+E9fjkPVTAolVEEh=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=lgz3yxkZf2MdvGK1AKPHmdmgMH198TsVJJ4N4+kPuse0kMVABmVKoEbxUS28kA1CQO9NRWQ1TE4Sbz+kYaKWA6hO9/BKHCsEkzqVx2d1Csi230CS+gfIbTEcGu1FaC1g0czVlICGduhnTiTf5IXO1JKPA1OkPm+jSf5CJQ7Ya42my06TJ1PtfN9wB+8q0aCC3iT+GNDA581J/0wdl9D1UIxXqQmHay1p3787yhHf/7J1ueybE+ec7X2mXvxXcdboY1lrR6jheFr2H2tFqZLKsVqVo8xh9N2tfvAQpBmNz1nOu70uaX88ZoeYCoyLPxt8T7IVVWHwndhPE239NG+uFQ== X-YMail-OSG: 4wIhXP4VM1lgFWof9twJrG9fRI3gL3OI.1MhUO.eOq27ry0V4XGBQnF0ZF8uuJ8 WUq_c6KADlC5xXkwVFp6Sgd_MuyZgYrEChhUJlcu._dB7TF1J2P.zKO5JjFQcjz.BtlR87B_KqXo tGszMRd6OLFwg_MtKbJ9GQ.5W6oOXVHsMATAJNPTv9djQ15_UQ52UXomQbCrSxOtrY1eOwUzg4NQ 9vL9oeRqo72RAEiCr4vzHBD9Y9ZAr71C78519wKRECyooLCcGZ1Y.2p.ee4IphfAoLM_C_QSD.EA SDWr8cMB18P8XRp5rXTunJwCg7pXbXgVoGlQ9rSQIt_e88PupF0dS9TKeKpFhnlkhGpq8XWCwFYu 8dTtLqjTtl_pIDy3QIgbboD6_w_AH9BnScVSSFQ_v1qdohallXiSvjsB6HbSTKl.W7QAbHbg6D5X nuVFWCaRbbTcBTWsvy9lxTugw0dD5xENS6SH3NRpTKV8.o8fgetFsNgZnBnyvbQxd_Rw1HrY3sp5 BkEuh04a0WpguJB_26JUvLO2K2YgarKbpAfB6zpJh_f3GO2jUC2hl.Tib1CQqK40j2ijeVFJ4Xys ubV0b3EC34lIA9DRhMC.qb5aoRmGoBQ64yJ7lrFjl.Rn4gMvEfu1CeNbkqpJQd1_BTrjx7AzEwP_ sPkjNUi9Ns2oCDkEVHBxihPl2ORSZDPnbSW5KYptSFn6FjIsDLqgS8yRHHfF9LtlbDf5edrRAvRP 8MVBmh4_7I98cBr7egjxwUXFuNBnzy8DoUUBY8vkyVqt5A4XBTMhdDo_QbFhvt.1HM2joxk5is8J dHXIIkQ.c8EvBkk1Vbr48DXnx_jWU0rnhj0C.HdfPFi4OcXeeaNkMJThqlg63MZsEev1FZNSMV_3 S9Q9esk9KlU3P1RfUKnbWwGlsept5fcHVUYT.updBsby5fq594410ykIJEcGTPkCX8Iv3.qRn8Ne X1v0bmle3gn4hZMbMZjQxhYr_4moTt7OzW6.ppkohnkD8pRck138QcPm6xn74u2ClCbcJJIZeG7I pkpMl0ZLxHaGSHATT8S9ZZ6tvRY3IY5jW7fvC1srCQeyeI1MjwzkrQ5DbVWCDelBogbSzuJ89wIW ts_JPWQcXUQjHNrjZ.G1db7PNRoVw3zgm0VUnlkZvC4oJcAWmRYYXjUoDzpZbhWOCtSW_Vmy.T7l eM5b4CQVrHF8SszPkmWH123KDDCIbKS78brselVOkA_EN0tDHQZ5odZzh4SQDwtJUuQsmiqrvAPu XN30O9LX1469y5BNQVW8ox6euTRt9alKkFgZuOl8B2rcEjKrxwlh33qyk5IV4ADGudd_w0qfBrxJ aE8Hnas1esujUVnyWNHQZQv9Er3Mw_jmawRW_4PKvCiQgpvfRxayZED0kt30pYv_vEN_f6qQT3NM Cua1OAH41AW70qqHLHK3v_DT8fjBRGw7E.AVLJBZfx9eVt2TkafDtotELc1gTB5AerN1mbZeuLiK VicFs4CX4ony1FGxDaf7HL3565OmrWw3GiXwGFGPDuRfX5Qa3jUUO5eHkfEf4m8Il_9LhjlnjnD9 kvHP99L_cFqcg0s0eRjlnZoYjepJWl2rS0ve5oPfd3Kk15YN6PeDMQHJ9DCxClWf_m8fSENxY2dR dI2nmB.4pTaKJk07fZdZbA3NAhHPoNFCi8iSGXeeAJtMmGq90U7_pw4WfMGpukGcbik66HYVK127 5rejU3EUCsYbLNxQ25xnmaVNdm2sIhLUHGkzgfhsDm97nevuO15Uure4Lrsd_0nyGbMLq13NuMxX FKD7NKyqmp5aXiW87iJ3x617owP8voEsAreWY8qxcqomdgiGimPZFqDwwX3Dh_lfbK.g74ruNPf3 051.Tr8_0MS2xqf8.EiSxi3D9.6YrQ5PKRMcNKicwaXBjYC1YYlMQIY94xArH02Bbiqtahsg49XJ jm1bQ9k5lb88x2mn3bu7byZcglH2yeMmOyKbhozF4fBPaTYy7AqfOUHYE0eyO8A9NalwiCueEyhD Mmh9BK0ygfo_QhC6GbrExQ3GgEJk5yUgufzLhA_UEbfQRA9zfZpCFZxbuUY1EISHNKMh6cw6mB8g exJCaB.PBh6.qwRqdYaxuyW6NqcWIoGJsAaYZGO_v6h3Nb2C4HofvKy5WaAds3r8vQHQ1pgJlNHc .rtH_7b4pywDzT0NZ_mLeUf3nQVHtqo1fygczr.lxvEbHXXCci0D.hgeztnYSuwA.Jtsre6zkiqM vwkrMj.5ewKHeM_EDbQR4lLzO7PS.tHGbALHt7FIhG3A3EVKilvzXoeeBGf4- X-Sonic-MF: X-Sonic-ID: 0bdd1470-c920-4009-9020-8c523b9b6b12 Received: from sonic.gate.mail.ne1.yahoo.com by sonic304.consmr.mail.ir2.yahoo.com with HTTP; Wed, 22 Jul 2026 16:18:56 +0000 Date: Wed, 22 Jul 2026 16:18:51 +0000 (UTC) From: Hannes Domani To: Simon Marchi via Gdb-patches , Pedro Alves Message-ID: <1310341683.1974283.1784737131422@mail.yahoo.com> References: <1310341683.1974283.1784737131422.ref@mail.yahoo.com> Subject: Re: [PATCH] Windows gdb: Fix resetting of the debug-registers bit in ContextFlags MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Mailer: WebService/1.1.26180 YMailNorrin X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: gdb-patches-bounces~public-inbox=simark.ca@sourceware.org Am Mittwoch, 22. Juli 2026 um 17:55:58 MESZ hat Pedro Alves Folgendes geschrieben: > On 2026-07-22 15:55, Hannes Domani wrote: >=C2=A0 > >>> Am Montag, 6. Juli 2026 um 17:02:35 MESZ hat Hannes Domani Folgendes geschrieben: > >>> > >>>> It's just great that all your mails are blocked by yahoo... > >>=C2=A0=C2=A0 > >> Sorry, but I don't know what I can do about that.=C2=A0 My hosting pro= vider, including email is dreamhost, > >> which is quite popular and I believe used by others in the community t= oo.=C2=A0 I don't have anything special > >> going on with my email AFAIK. > > > > I know, it's just very frustrating. >=C2=A0 > Is this only about emails sent to the mailing list, i.e., ones that are s= ent to you by sourceware's Mailman, > not me directly?=C2=A0 Do you receive the direct copy when I To: you dire= ctly, like this one? No, I didn't get this one either. I did ask about this some time ago on #overseers: Apr 30 17:39:57 sourceware postfix/smtp[3802111]: 9DBF1436A055: to= =3D, relay=3Dmx-eu.mail.am0.yahoodns.net[188.125.72.74]:25= , delay=3D2.3, delays=3D0.11/0/0.82/1.4, dsn=3D5.7.9, status=3Dbounced (hos= t mx-eu.mail.am0.yahoodns.net[188.125.72.74] said: 550 5.7.9 This mail has = been blocked because the sender is unauthenticated. Yahoo requires all send= ers to authenticate with either SPF or DKIM. Authentication results: DKIM = =3D FAILURE=C2=A0 - SPF palves.net with ip X.X.X.X =3D FAILURE. See https://senders.ya= hooinc.com/smtp-error-codes/#authentication-failures for more information. = (in reply to end of DATA command)) and yeah yahoo appears to be doing nothing RFC-violating. It just de= mands DMARC alignment; pedro's domain doesn't DKIM-sign outgoing messages, = and without from: rewriting, the sourceware-relayed email's From: still loo= ks like palves.net, which then nukes the DMARC SPF alignment. With neither = DKIM nor SPF alignment, DMARC fails. ssbssa, yeah, yahoo.de seems even pickier than other yahoo, but it is= generic problem with yahoo in general. They try to do dmarc "alignment" ev= en if the sender doesn't support it. They should fall back to sender spf (w= hich sourceware does set correctly) but don't. > > Even more so because you recently submitted more windows-related stuff. >=C2=A0 > FWIW, I subscribe to the mailing list using my gmail account, but nobody = ever sees that, because > I always respond with my palves.net email address.=C2=A0 I use Thunderbir= d, and there the "Correct Identify" > add-on is super useful for this -- I have it set up to that when I reply = to an email from the sourceware > domain that I received on the gmail inbox, the thunderbird email writing = windows automatically pops with with > my palves.net address as the default sender. >=C2=A0 > In a nutshell, I freeload on gmail as my public mailing list storage.=C2= =A0 It's all archived public messages, > so I'm fine with that.=C2=A0 :-) >=C2=A0 > If this is only about the mailing list emails, maybe a setup like that wo= uld work for you, too. I'll probably have to look into something like this, because it got a lot w= orse in the last year. > >>>>>> --- > >>>>>>=C2=A0 =C2=A0gdb/x86-windows-nat.c | 10 +++++++--- > >>>>>>=C2=A0 =C2=A01 file changed, 7 insertions(+), 3 deletions(-) > >>>>>> > >>>>>> diff --git a/gdb/x86-windows-nat.c b/gdb/x86-windows-nat.c > >>>>>> index 27adeb1f154..3368814ed96 100644 > >>>>>> --- a/gdb/x86-windows-nat.c > >>>>>> +++ b/gdb/x86-windows-nat.c > >>>>>> @@ -42,6 +42,10 @@ enum > >>>>>>=C2=A0=C2=A0 > >>>>>>=C2=A0 =C2=A0#define DR6_CLEAR_VALUE 0xffff0ff0 > >>>>>=C2=A0=C2=A0 > >>>>>>=C2=A0=C2=A0 > >>>>>> +/* The CONTEXT_DEBUG_REGISTERS define without the arch-specific b= it > >>>>>> +=C2=A0 (CONTEXT_i386 or CONTEXT_AMD64).=C2=A0 */ > >>>>>> +#define CONTEXT_DEBUG_REG_FLAG 0x10 > >>>>>> + > >>>>>=C2=A0=C2=A0 > >>>>> Did you consider avoiding harcoding numbers, like: > >>>>>=C2=A0=C2=A0 > >>>>> #ifdef __x86_64__ > >>>>> # define CONTEXT_ARCH_BIT CONTEXT_AMD64 > >>>>> #else > >>>>> # define CONTEXT_ARCH_BIT CONTEXT_i386 > >>>>> #endif > >>>>>=C2=A0=C2=A0 > >>>>> #define CONTEXT_DEBUG_REG_FLAG (CONTEXT_DEBUG_REGISTERS & ~CONTEXT_= ARCH_BIT) > >>>>=C2=A0=C2=A0 > >>>> I did consider this: > >>>>=C2=A0=C2=A0 > >>>> #define CONTEXT_DEBUG_REG_FLAG (CONTEXT_DEBUG_REGISTERS & ~CONTEXT_C= ONTROL) > >>=C2=A0=C2=A0 > >> OK, so why did you decide against it? > > > > I didn't really have a good reason, so I'll do it like this in v2. >=C2=A0 > Hmm, I hadn't looked at CONTEXT_CONTROL's definition before.=C2=A0 I did = now: >=C2=A0 > #define CONTEXT_AMD64 0x100000 > #define CONTEXT_CONTROL (CONTEXT_AMD64 | __MSABI_LONG(0x1)) >=C2=A0 > So it's more then the arch bit?=C2=A0 Is that really correct to use here? It's not conflicting with the debug-registers bit, so it should be fine. > >>>> I did some experiments, and it looks like SetThreadContext doesn't c= are at > >>>> all about the arch bit, so it is working like your original intentio= n. > >>>> I thought it would fail in the arch bit is missing, but I was wrong = about that. > >>>>=C2=A0=C2=A0 > >>=C2=A0=C2=A0 > >> Seeing this, FYI, I didn't know if you planed on dropping the patch, o= r sending an > >> updated one with a commit log that reflects the finding.=C2=A0 But I d= idn't think the > >> current one as it was, was ready. > > > > This was also a point where I thought you would give some comment, I > > was wrong about that too. > > > > So, when in doubt, I should send an updated patch? > > >=C2=A0 > I'm not sure we can come up with a rule.=C2=A0 :-)=C2=A0 I guess what I m= issed is a question > instead of a statement.=C2=A0 I'll try to avoid assuming as much too. Thanks Hannes