From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id ADTVGpiddWDNMwAAWB0awg (envelope-from ) for ; Tue, 13 Apr 2021 09:33:12 -0400 Received: by simark.ca (Postfix, from userid 112) id 605F61F104; Tue, 13 Apr 2021 09:33:12 -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.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.2 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 CBFFD1E01F for ; Tue, 13 Apr 2021 09:33:10 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 5070F39450F1; Tue, 13 Apr 2021 13:33:10 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5070F39450F1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1618320790; bh=jVVPqMS0TfRzLqOqMqFW5vRZgKgZNlbeckABuWq4N04=; h=Subject:To:References:Date:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=aaIlYO8fPF3j2Pl/zYSFnaP4LRkouPUPeOCf98I8yXBbtOxRrMvK24o/pwX1A8Bex OfgeztAkEpYqyR0QX947Xo1bIWoYiLEjp2HZkxy1+d4jK2aJ0ypcGtq8YQhkyX+4TM 3MzPhorVdbjcXtkUvt86wVHvuIsGPg6JXF3MCEMU= Received: from mail-qk1-x733.google.com (mail-qk1-x733.google.com [IPv6:2607:f8b0:4864:20::733]) by sourceware.org (Postfix) with ESMTPS id 2A616385702C for ; Tue, 13 Apr 2021 13:33:08 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 2A616385702C Received: by mail-qk1-x733.google.com with SMTP id 130so3577668qkm.4 for ; Tue, 13 Apr 2021 06:33:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=jVVPqMS0TfRzLqOqMqFW5vRZgKgZNlbeckABuWq4N04=; b=Ly/JIj7kcSx1gHBoFQGKq47/Yu0Q6BCJHHWRhQv31er0wJEgzpgj3ABcjiOZfPu3S0 mXOXshmQxXlSb4GFt+EJwL1uJvIhchFnQGHqGtwbJ8Q/L6JB5WZ6UOLUyC9qJV+lfUQQ qTwUsujjiUbzR3rc77o1V4yfY8csDqixFNJYTQkhoy2aXoLApiiZoFpJqoEYkflknK2Q +iTsL571bPT8taVrQs6bCcH05ewQM3oIw4YxG5q1N4cPfOnl6eIs7IvJUERX4jbCYekG ZDH3oFIQjFqautt7eB8bqUsGpQZ8QZoikRHxNS4sfHgVUfeIz2qWDDNDkyawbhxj459C 0BxQ== X-Gm-Message-State: AOAM531or9STiX93aiMktk3BKRbbI5qwTWvnsrbJyuOcQZFwPfj/Lpyj Q4R2vFt+M9kCo7zwR3RmJVIeww== X-Google-Smtp-Source: ABdhPJzJNAyYTAHbOB8QQBVHQ+a0/4Gio+XfSWvjeBwluCxRWCy21/+4cs5SVxV6u3kmJiyNOUEM7w== X-Received: by 2002:ae9:f70a:: with SMTP id s10mr32564483qkg.468.1618320787695; Tue, 13 Apr 2021 06:33:07 -0700 (PDT) Received: from ?IPv6:2804:7f0:4841:2841:b15b:1248:f1ec:bed5? ([2804:7f0:4841:2841:b15b:1248:f1ec:bed5]) by smtp.gmail.com with ESMTPSA id f16sm3035759qkl.25.2021.04.13.06.33.05 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 13 Apr 2021 06:33:07 -0700 (PDT) Subject: Re: [PATCH][gdb/testsuite] Fix gdb.threads/killed-outside.exp with -m32 To: Tom de Vries , gdb-patches@sourceware.org References: <20210118114422.GA11394@delia> Message-ID: <208b6e38-66f5-0395-62f7-9f122384a3a5@linaro.org> Date: Tue, 13 Apr 2021 10:33:02 -0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: <20210118114422.GA11394@delia> Content-Type: text/plain; charset=utf-8; format=flowed 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: , From: Luis Machado via Gdb-patches Reply-To: Luis Machado Cc: Pedro Alves Errors-To: gdb-patches-bounces@sourceware.org Sender: "Gdb-patches" I was looking at this test on aarch64-linux/x86_64-linux Ubuntu 20.04 and noticed inconsistent output. I'm trying to assess what is the best course of action. On 1/18/21 8:44 AM, Tom de Vries wrote: > Hi, > > When running test-case gdb.threads/killed-outside.exp with target board > unix/-m32, we run into: > ... > (gdb) PASS: gdb.threads/killed-outside.exp: get pid of inferior > Executing on target: kill -9 10969 (timeout = 300) > spawn -ignore SIGHUP kill -9 10969^M > continue^M > Continuing.^M > [Thread 0xf7cb4b40 (LWP 10973) exited]^M > ^M > Program terminated with signal SIGKILL, Killed.^M > The program no longer exists.^M > (gdb) FAIL: gdb.threads/killed-outside.exp: prompt after first continue > ... > > Fix this by allowing this output. > > Tested on x86_64-linux. > > Any comments? > > Thanks, > - Tom I see the following output, most of the time: Executing on target: kill -9 3742839 (timeout = 300) spawn -ignore SIGHUP kill -9 3742839^M continue^M Continuing.^M Unable to fetch general registers.: No such process.^M (gdb) [Thread 0xfffff7e281e0 (LWP 3742842) exited]^M ^M Program terminated with signal SIGKILL, Killed.^M The program no longer exists.^M FAIL: gdb.threads/killed-outside.exp: prompt after first continue (timeout) But I also see the following with READ1: Executing on target: kill -9 3743271 (timeout = 300) spawn -ignore SIGHUP kill -9 3743271^M continue^M Continuing.^M Unable to fetch general registers.: No such process.^M (gdb) FAIL: gdb.threads/killed-outside.exp: prompt after first continue Besides the messages not being the same, there is some odd inconsistency with the prompt positioning compared to what you mentioned above. Forcing scheduler-locking to on made the output consistent for both cases, but I was left wondering if enabling scheduler-locking would cause the bug to not be reproducible anymore. Thoughts?