From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8549 invoked by alias); 12 Feb 2016 16:36:49 -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 8515 invoked by uid 89); 12 Feb 2016 16:36:48 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy= 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; Fri, 12 Feb 2016 16:36:48 +0000 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (Postfix) with ESMTPS id 08FDF32D3C7; Fri, 12 Feb 2016 16:36:46 +0000 (UTC) Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u1CGajPY027264; Fri, 12 Feb 2016 11:36:45 -0500 Message-ID: <56BE0A1D.2070408@redhat.com> Date: Fri, 12 Feb 2016 16:36:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Luis Machado , gdb-patches@sourceware.org CC: gbenson@redhat.com Subject: Re: [PATCH] Remote debugging without a binary (regression) References: <1455200365-5270-1-git-send-email-lgustavo@codesourcery.com> <56BDFA73.9000001@redhat.com> <56BE038E.3060406@codesourcery.com> In-Reply-To: <56BE038E.3060406@codesourcery.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SW-Source: 2016-02/txt/msg00419.txt.bz2 On 02/12/2016 04:08 PM, Luis Machado wrote: > I did not exercise that, but did not discard it either. I was attempting > to solve one problem at a time. There may be a failure there too. I matters to determine where the TRY/CATCH should go, or even whether the fix should be to not throw in the first place. Like, with: (gdb) define foo > attach PID > info threads > end (gdb) foo should failing to load the executable error out before reaching "info threads", or continue. I think it should not error out, like we don't error out if the target doesn't support target_pid_to_exec_file at all. Thanks, Pedro Alves