From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1370 invoked by alias); 26 Sep 2002 22:43:11 -0000 Mailing-List: contact insight-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sources.redhat.com Received: (qmail 1363 invoked from network); 26 Sep 2002 22:43:10 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 26 Sep 2002 22:43:10 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id g8QMP2i18502 for ; Thu, 26 Sep 2002 18:25:02 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id g8QMh9f12609; Thu, 26 Sep 2002 18:43:09 -0400 Received: from valrhona.uglyboxes.com (IDENT:oqrY0KvkHseHsclzCgCKd8sYCbfNRxcJ@vpn50-53.rdu.redhat.com [172.16.50.53]) by pobox.corp.redhat.com (8.11.6/8.11.6) with ESMTP id g8QMh8J23421; Thu, 26 Sep 2002 18:43:08 -0400 Date: Thu, 26 Sep 2002 15:43:00 -0000 From: Keith Seitz X-X-Sender: keiths@valrhona.uglyboxes.com To: Paul Breed cc: insight@sources.redhat.com Subject: Re: Insight Shutdown behavior In-Reply-To: <5.0.2.1.2.20020926154004.03470350@mail.netburner.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-q3/txt/msg00194.txt.bz2 [moved to insight list] On Thu, 26 Sep 2002, Paul Breed wrote: > When debugging with Insight as a cross debugger > under windows one has to shutdown so that > you can rebuild the elf file you are debugging. > (Otherwise you have a sharing violation) What's your target? As I recall, this is not an Insight bug. I don't even think it's a gdb bug. I remember this came up a long time ago... > This is not totally unreasonable, but the really anoying part is that > insight can randomly decide to take 20 or 30 seconds to shutdown. Mine certainly doesn't take this long, even on windows. > Any suggestions on: > > 1)Leaving Insight open, and closing the file being debugged > so one can rebuild? Umm... File->Close? > 2)Figuring out what takes so long when Insight shuts down. What release are you using? Type "gdb -v". Also when you run Insight, open a console window and type "tk info tclversion". What's the result? If you want to debug it, I would try starting insight under gdb and setting a break in gdb_force_quit. This is the place where shutdown starts. Keith