From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 73817 invoked by alias); 23 May 2018 12:04:07 -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 73315 invoked by uid 89); 23 May 2018 12:04:06 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.9 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy= X-HELO: mx1.redhat.com Received: from mx3-rdu2.redhat.com (HELO mx1.redhat.com) (66.187.233.73) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 23 May 2018 12:04:05 +0000 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com [10.11.54.4]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id C274940711A1; Wed, 23 May 2018 12:04:03 +0000 (UTC) Received: from [127.0.0.1] (ovpn04.gateway.prod.ext.ams2.redhat.com [10.39.146.4]) by smtp.corp.redhat.com (Postfix) with ESMTP id 151E22026987; Wed, 23 May 2018 12:04:02 +0000 (UTC) Subject: Re: [PATCH] testsuite: Extend TLS core file testing with an OS-generated dump To: "Maciej W. Rozycki" , gdb-patches@sourceware.org References: Cc: Djordje Todorovic From: Pedro Alves Message-ID: <5b76142d-479d-3c34-9294-9f4510d0fc04@redhat.com> Date: Wed, 23 May 2018 13:35:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2018-05/txt/msg00623.txt.bz2 On 05/23/2018 12:10 AM, Maciej W. Rozycki wrote: > to gdbserver testing. The latter is because we'd have to handle core > file copying from the remote system and then cleaning up with a possibly > variable name of the core file created. This code has been based on > gdb.base/auxv.exp, which does not do it either. Hmm, that sounds like an outdated testcase to copy. See gdb.threads/corethreads.exp, for example, and the use of the core_find procedure. Can we use that procedure here too? I also don't see why (gdbserver && !is_remote) testing can't work, such as with --target=native-gdbserver and --target=native-extended-gdbserver boards. It works for gdb.threads/corethreads.exp, for example. Thanks, Pedro Alves