From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27942 invoked by alias); 5 Nov 2009 18:58:47 -0000 Received: (qmail 27933 invoked by uid 22791); 5 Nov 2009 18:58:47 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from m98.hosting.altserver.com (HELO m98.hosting.altserver.com) (72.34.46.98) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 05 Nov 2009 18:58:40 +0000 Received: from help3.essnet.com ([208.249.80.247]:49271 helo=HELP3) by hosting.altserver.com with esmtpa (Exim 4.69) (envelope-from ) id 1N67Xb-0005Tb-1i; Thu, 05 Nov 2009 10:58:39 -0800 Message-ID: <53D4AFC3249C4B4CB6EBE58C08CD52B1@HELP3> From: =?iso-8859-1?Q?Mar=EDa_de_los_A._V=E1zquez?= To: "Keith Seitz" Cc: References: <4AEF4006.8020604@redhat.com> <50C6D56245CE4AFDBA0A2853C2CA378D@HELP3> <4AEF54E4.2070209@redhat.com> <519FEDB294554B38AA780E6E14D10F98@HELP3> <4AF1CAFA.2080209@redhat.com> <3016172ABB7447CB8ED230D87BCDDD02@HELP3> <4AF1D3A5.1040804@redhat.com> <6A1B4B1ABAF141398311A422FFC59D67@HELP3> <4AF1E67F.6030201@redhat.com> <4AF1F2C3.3070908@redhat.com> <32C38ADA3F3643C9A0F37DFCDAEAAA4F@HELP3> <4AF30419.2080204@redhat.com> In-Reply-To: <4AF30419.2080204@redhat.com> Subject: Re: Fw: Initialization Commands Date: Thu, 05 Nov 2009 18:58:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Mailing-List: contact insight-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sourceware.org X-SW-Source: 2009-q4/txt/msg00021.txt.bz2 > That all looks good. Can you start insight and manually > attach/download/run to main using the console? (i.e, "break main", "target > remote localhost:3333", "load", "continue") Yes. I can use it without problems. > If insight is timing out, it is usually a communication failure. You could > also try opening a debug window for more info (open console window, enter > "tk ManagedWin::open DebugWin"). You might be able to use some of gdb's > built-in debugging/diagnostics to see what's happening with the target > (enter "help set debug remote" -- never tried this with insight, though). I can only test this when I'm running insight manually. If I start insight using the Run button it stays Not Responding. I will not have problems If I have to manually attach/download/run to main using the console but I need at least that insight could save my new breakpoints. Isn't nice at all to set several breakpoints, close insight and when you open it again noticed that they weren't saved but even If you open it few days later. Not everybody could remember which breakpoints were set previously if they were several. María