From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 116701 invoked by alias); 24 Jul 2015 16:05:56 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 116692 invoked by uid 89); 24 Jul 2015 16:05:56 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: relay1.mentorg.com Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 24 Jul 2015 16:05:54 +0000 Received: from svr-orw-fem-05.mgc.mentorg.com ([147.34.97.43]) by relay1.mentorg.com with esmtp id 1ZIfTq-0001ON-EV from Sandra_Loosemore@mentor.com ; Fri, 24 Jul 2015 09:05:50 -0700 Received: from [IPv6:::1] (147.34.91.1) by svr-orw-fem-05.mgc.mentorg.com (147.34.97.43) with Microsoft SMTP Server id 14.3.224.2; Fri, 24 Jul 2015 09:05:49 -0700 Message-ID: <55B261EF.8010801@codesourcery.com> Date: Fri, 24 Jul 2015 16:05:00 -0000 From: Sandra Loosemore User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130329 Thunderbird/17.0.5 MIME-Version: 1.0 To: Gary Benson CC: "gdb@sourceware.org" Subject: Re: GDB now takes 4 minutes to start up with remote gdbserver target References: <55B1768E.9090309@codesourcery.com> <55B1A4FC.9010403@codesourcery.com> <20150724103406.GA1653@blade.nx> In-Reply-To: <20150724103406.GA1653@blade.nx> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2015-07/txt/msg00048.txt.bz2 On 07/24/2015 04:34 AM, Gary Benson wrote: > Sandra Loosemore wrote: >> (4) GDB doesn't respond to ^C during the 4 minutes it is doing >> whatever it's doing to transfer files. It just sits there acting >> catatonic. > > Sandra, could you tell me if this patch makes GDB interruptible for > you? No, it is not doing anything to help. It only notices the ^C when it finishes whatever it is doing and reaches the breakpoint at main, same as before. Also, what kind of state would you expect GDB to be left in, if it could be interrupted? It might be somewhat reassuring to users to get back to a gdb prompt so they know it's still alive, but if there's nothing to indicate what was taking so long and any attempt to continue debugging the program results in another long delay while the file transfer is retried, that wouldn't be helpful. -Sandra