From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id 6QW0CZtKl2PMoSYAWB0awg (envelope-from ) for ; Mon, 12 Dec 2022 10:36:59 -0500 Received: by simark.ca (Postfix, from userid 112) id 1AC831E124; Mon, 12 Dec 2022 10:36:59 -0500 (EST) 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=bFTiioG2; 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=-8.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI, 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 9FD181E0CB for ; Mon, 12 Dec 2022 10:36:58 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 9171E3852209 for ; Mon, 12 Dec 2022 15:36:57 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9171E3852209 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1670859417; bh=r8DUJK9BtGFFpMgluM1GWZ+rDzEdXoHpQtIsuenEKyI=; h=To:Cc:Subject:References:Date:In-Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=bFTiioG2bk5bRIhklw6zwNwiwotWKp10DfXbsTujsajlp8O5AUkZlmahZbGJH6SRm 9fY1vVwsDAkn4DLf++EQyr2rlkvrTQuXhlPfeqGu5QbHcWjw5KV2zln5m3+g0682Vx drHqQATZhEub8C/j0KxCvJJaQ16QEbzWqMejQN1c= Received: from mail-yw1-x112f.google.com (mail-yw1-x112f.google.com [IPv6:2607:f8b0:4864:20::112f]) by sourceware.org (Postfix) with ESMTPS id 396C0385F3C4 for ; Mon, 12 Dec 2022 15:36:37 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 396C0385F3C4 Received: by mail-yw1-x112f.google.com with SMTP id 00721157ae682-3bf4ade3364so151543587b3.3 for ; Mon, 12 Dec 2022 07:36:37 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:user-agent:message-id :in-reply-to:date:references:subject:cc:to:from:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=r8DUJK9BtGFFpMgluM1GWZ+rDzEdXoHpQtIsuenEKyI=; b=n95N5z8wkES1bHsrLD7SbXtQqGrEaaR9/aJ831Ze8L4/ltsFDuI5o2JkcrLZ7mN3md D2kE9UMeEcN0G5CQHLCz8drh/R+Kv3x7jji4Gd535wdfDmsCflFqU6N8ZhzAV221I+gW Du9R+4hgRghMW7jCjSfN9Iz/sv3woIfsVjEDBaASLKBAkbYv8tVmP00Z6oC0sNdK/wA3 jR+eu4+ZAwH7K+DJxAU/SSXB29WJi0LMxqr/fQliH0qKe0tKeSOBLiq8XKSr+Lr2L5EG g5/S/+SNYNv6G8Vn2lB+pAFE7QgXghLrqwYRizNSys1TF9p9t3rZXFTPuMCQWPBoQ5Mi qCEA== X-Gm-Message-State: ANoB5pmJ0k0kDLhWQ/50SKgQOX5qiD8D3Fz+xmyqFgO/Ht2nisPrU9SV w/YcUvmP+D6MOygQy4rFq7w4vQ== X-Google-Smtp-Source: AA0mqf7+2WMfU4nhltkfvbbv7GoEF5oMEo+hTqZyvJRjEl8H9L7pryWQUtuDkgz84fQ7kr+yKWfg4w== X-Received: by 2002:a0d:c386:0:b0:3eb:bf55:1c4f with SMTP id f128-20020a0dc386000000b003ebbf551c4fmr12535090ywd.33.1670859396599; Mon, 12 Dec 2022 07:36:36 -0800 (PST) Received: from murgatroyd ([2620:20:4000:100::1000]) by smtp.gmail.com with ESMTPSA id l6-20020a37f906000000b006fbb4b98a25sm5869996qkj.109.2022.12.12.07.36.34 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 12 Dec 2022 07:36:35 -0800 (PST) To: Hannes Domani Cc: Tom Tromey , "gdb-patches@sourceware.org" Subject: Re: [PATCH 3/3] Fix control-c handling on Windows References: <20221205185651.2704492-1-tromey@adacore.com> <20221205185651.2704492-4-tromey@adacore.com> <102195784.4047621.1670433222150@mail.yahoo.com> <87ilikin72.fsf@tromey.com> <1095715284.5500968.1670602756752@mail.yahoo.com> <87edt8ijd7.fsf@tromey.com> <127884065.5583846.1670609613440@mail.yahoo.com> X-Attribution: Tom Date: Mon, 12 Dec 2022 08:36:32 -0700 In-Reply-To: <127884065.5583846.1670609613440@mail.yahoo.com> (Hannes Domani's message of "Fri, 9 Dec 2022 18:13:33 +0000 (UTC)") Message-ID: <87cz8ohbwf.fsf@tromey.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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: Tom Tromey via Gdb-patches Reply-To: Tom Tromey Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" Hannes> Again, I wasn't clear enough here. Hannes> The difference is not because of i686 and x86_64, but that the x86_= 64 build Hannes> has TUI+python enabled, but my i686 build has not. >> Aha, I see, thanks. Today I built an x86-64 Windows gdb, but I disabled Python. I already had the TUI disabled for Windows. I used RDP and started powershell, then ran gdb there. I did 6 tests: a C-c and a C-break test of "run", "run" with "set new-console 1", and "attach" -- and in all these cases, it worked. So now I'm wondering again what the difference could be between our situations. >> Anyway I am wondering if we can have gdb_rl_deprep_term_function call >> rl_clear_signals and then reinstall the gdb signal handlers.=C2=A0 This = idea >> makes me wonder if we even need SetConsoleCtrlHandler at all -- maybe gdb >> could just use signal after all. Hannes> Good question, maybe it doesn't handle C-break as well? C-break can work with signal by installing a handler for SIGBREAK. This worked fine when I tried it, but the issue was still that the SIGINT handler somehow stopped working. Tom