From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 101231 invoked by alias); 6 Apr 2015 11:26:28 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 101221 invoked by uid 89); 6 Apr 2015 11:26:26 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Mon, 06 Apr 2015 11:26:25 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id t36BQNhf017848 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Mon, 6 Apr 2015 07:26:23 -0400 Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t36BQLW4028132; Mon, 6 Apr 2015 07:26:22 -0400 Message-ID: <55226D5D.3020200@redhat.com> Date: Mon, 06 Apr 2015 11:26:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Yao Qi , gdb-patches@sourceware.org Subject: Re: [PATCH 8/8] add non-stop test that stresses thread starvation issues References: <1419625871-28848-1-git-send-email-palves@redhat.com> <1419625871-28848-9-git-send-email-palves@redhat.com> <551D57CC.9050403@gmail.com> In-Reply-To: <551D57CC.9050403@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2015-04/txt/msg00143.txt.bz2 On 04/02/2015 03:53 PM, Yao Qi wrote: > Hi, Pedro, > > On 26/12/14 20:31, Pedro Alves wrote: >> +int >> +main (void) >> +{ >> + int res; >> + int i; >> + >> + alarm (60); > > Is there any reason to call alarm here? Yes, the test runs forever otherwise. See: https://sourceware.org/gdb/wiki/GDBTestcaseCookbook#Don.27t_write_tests_that_run_forever How about fixing this like attach-many-short-lived-threads.exp was fixed here: https://sourceware.org/ml/gdb-patches/2015-02/msg00152.html ? > It causes some fails on > arm-linux, that is, the board is slow, and alarm is triggered. > Then thread is disappeared and current_thread is set to NULL. > GDB/GDBserver doesn't know about that. When the inferior memory is > accessed, current_thread is dereferenced, and GDBserver is crashed. Sounds like we should have a test that explicitly covers that. GDBserver shouldn't crash. -- Pedro Alves