From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id +JEhColbU2E/CwAAWB0awg (envelope-from ) for ; Tue, 28 Sep 2021 14:14:33 -0400 Received: by simark.ca (Postfix, from userid 112) id 172CC1EE25; Tue, 28 Sep 2021 14:14:33 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-1.6 required=5.0 tests=MAILING_LIST_MULTI, NICE_REPLY_A,RDNS_DYNAMIC,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (ip-8-43-85-97.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 3C95F1EDDB for ; Tue, 28 Sep 2021 14:14:32 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id AC84D3858023 for ; Tue, 28 Sep 2021 18:14:31 +0000 (GMT) Received: from mail-wm1-f46.google.com (mail-wm1-f46.google.com [209.85.128.46]) by sourceware.org (Postfix) with ESMTPS id 511893858D39 for ; Tue, 28 Sep 2021 18:14:21 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 511893858D39 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=palves.net Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gmail.com Received: by mail-wm1-f46.google.com with SMTP id d207-20020a1c1dd8000000b00307e2d1ec1aso3394776wmd.5 for ; Tue, 28 Sep 2021 11:14:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:from:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=hs7g4fqiJlUsAfeq+9WupUhX0ppKRVLWTp4f/lpAN6w=; b=p2uQ7G8/Ug6GuskdmVKBu/L9ZWTeiRQy2WuECfthBfvTdh+9W6YnGz2AuLFCokWbiq YEaSNyf6iMRN0TvEzm9ML1hRdFVyI0ixMeKKHQcyGq3L6/2Opxn8SmbOkOuDDQw+pUo1 TpiTYV+kL9B6osdd8E63sf6zMfUKpa7RpwWQXeCIxdNt2c2SSkha+zBq7CNVDxWq/m33 e/qyyUHs6qrqNIJ7Q391a0OkUuicOQgwEU0KLp0FBWu07NpiMkVQVllal/DNNySs3VmJ EnwC5j8wfV37GnPAsW36X3btNZLZB/MfxEGrIU2jub9ezdmwHT5MAZOO9FN5G19ylj8l jhSQ== X-Gm-Message-State: AOAM533j67NLZw6eCqYWy/X/RrxhHLPXmrrqISQzw0MqRvjHSgIlsIJ8 Gw36pY6iGvuXXEnhiBNvemFwB08cxoQ= X-Google-Smtp-Source: ABdhPJx21o7ywedYo29/mCSNI5SmnMeb1Bd6AoBkMWG9d7i72pNkIFlueWehHeG3fLTUbV2nbItQQw== X-Received: by 2002:a05:600c:3b21:: with SMTP id m33mr994892wms.80.1632852859647; Tue, 28 Sep 2021 11:14:19 -0700 (PDT) Received: from ?IPv6:2001:8a0:f932:6a00:46bc:d03b:7b3a:2227? ([2001:8a0:f932:6a00:46bc:d03b:7b3a:2227]) by smtp.gmail.com with ESMTPSA id s10sm20524466wrg.42.2021.09.28.11.14.18 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 28 Sep 2021 11:14:18 -0700 (PDT) Subject: Re: [PATCH][gdb/testsuite] Fix gdb.multi/multi-term-settings.exp From: Pedro Alves To: Tom de Vries , gdb-patches@sourceware.org References: <20210928175722.GA15861@delia> Message-ID: <81b6b3e3-12c4-e074-1b5d-70c7be375a11@palves.net> Date: Tue, 28 Sep 2021 19:14:17 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: <20210928175722.GA15861@delia> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit 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: , Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" On 2021-09-28 6:57 p.m., Tom de Vries wrote: > Hi, > > When running test-case gdb.multi/multi-term-settings.exp in conjunction with: > ... > $ stress -c $(($(cat /proc/cpuinfo | grep -c ^processor) + 1)) > ... > I run into: > ... > (gdb) PASS: gdb.multi/multi-term-settings.exp: \ > inf1_how=attach: inf2_how=attach: info inferiors > pid=14783, count=59^M > pid=14783, count=60^M > ... > pid=14783, count=118^M > pid=14783, count=119^M > pid=14778, count=90^M > pid=14778, count=91^M > pid=14778, count=92^M > pid=14778, count=93^M > pid=14778, count=94^M > pid=14778, count=95^M > PASS: gdb.multi/multi-term-settings.exp: inf1_how=attach: inf2_how=attach: continue > Quit^M > (gdb) FAIL: gdb.multi/multi-term-settings.exp: \ > inf1_how=attach: inf2_how=attach: stop with control-c (SIGINT) > ... > > It occurred to me that the "Continuing." we see otherwise is not shown and > that it's possible that the control-C that is send is caught by gdb when > printing this. > > Fix this by waiting for the "Continuing." message before sending control-C. > > Tested on x86_64-linux. > > Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=24929 > > Any comments? > Hmm, think rang a bell. I had posted a patch for this a few months back: https://sourceware.org/pipermail/gdb-patches/2021-June/179503.html The idea is the same, but my version is more complete, IMHO. Sorry I didn't think of splitting that one out of the series at the time, this could have been fixed all this time. :-/