From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12077 invoked by alias); 21 Feb 2007 07:45:19 -0000 Received: (qmail 12061 invoked by uid 22791); 21 Feb 2007 07:45:18 -0000 X-Spam-Check-By: sourceware.org Received: from main.gmane.org (HELO ciao.gmane.org) (80.91.229.2) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 21 Feb 2007 07:45:10 +0000 Received: from root by ciao.gmane.org with local (Exim 4.43) id 1HJm9u-00065W-Nx for ecos-discuss@sources.redhat.com; Wed, 21 Feb 2007 08:45:02 +0100 Received: from host217-34-45-110.in-addr.btopenworld.com ([217.34.45.110]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 21 Feb 2007 08:45:02 +0100 Received: from dlawrence by host217-34-45-110.in-addr.btopenworld.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 21 Feb 2007 08:45:02 +0100 To: ecos-discuss@sources.redhat.com From: Dave Lawrence Date: Wed, 21 Feb 2007 07:45:00 -0000 Message-ID: References: <771000.63523.qm@web62306.mail.re1.yahoo.com> <1170683150.7106.6.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) In-Reply-To: <1170683150.7106.6.camel@localhost> X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: [ECOS] Re: GDB stops randomly X-SW-Source: 2007-02/txt/msg00197.txt.bz2 I have also seen this with Insight, and annoyingly the GUI doesn't always indicate the presence of these breakpoints. If you delete gdbtk.ini (or less drastic, edit it) the problem goes away, at least, it goes away for the current build of code, if you add more breakpoints, then the problem will come back for a future build... Donald Walton wrote: > I have noticed this behavior when I use Insight. The cause was editing > the program in the area where a breakpoint had been set. The editing > process can leave the previously set breakpoint invalid. > > If you have breakpoints set when you go into your program, check them > before you run the program to verify they are still valid, i.e., on a > line of code. > > Don -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss