From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32740 invoked by alias); 9 Mar 2006 16:09:34 -0000 Received: (qmail 32720 invoked by uid 22791); 9 Mar 2006 16:09:33 -0000 X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 09 Mar 2006 16:09:31 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id k29G9UXs029738 for ; Thu, 9 Mar 2006 11:09:30 -0500 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 k29G9U129098; Thu, 9 Mar 2006 11:09:30 -0500 Received: from [127.0.0.1] (sebastian-int.corp.redhat.com [172.16.52.221]) by pobox.corp.redhat.com (8.12.8/8.12.8) with ESMTP id k29G9S51028876; Thu, 9 Mar 2006 11:09:29 -0500 Message-ID: <44105338.20004@redhat.com> Date: Thu, 09 Mar 2006 16:09:00 -0000 From: Keith Seitz User-Agent: Thunderbird 1.5 (X11/20060112) MIME-Version: 1.0 To: Guillaume Savaton CC: insight@sources.redhat.com Subject: Re: Make breakpoint pending References: <000101c63763$1e368fa0$ad00a8c0@amarnath> <4406B226.7090904@eseo.fr> In-Reply-To: <4406B226.7090904@eseo.fr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact insight-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sourceware.org X-SW-Source: 2006-q1/txt/msg00056.txt.bz2 Guillaume Savaton wrote: > Hi, > > I have been using previous versions of insight (5.x) for a while, and I > have > noticed a new message in 6.4 when I attempt to run a program : > "Make breakpoint pending on future shared library load?" Yeah, that happens when gdb is asked to set a breakpoint someplace that it knows nothing about (so it assumes that you have not made a mistake but that the location exists in a shared library). > This message is quite annoying since I am asked to confirm for each > breakpoint > in my program individually. Okay, I have not seen this before, and I cannot reproduce it with any testcase I've managed to devise. If you look at the breakpoints which were marked pending, are they part of your program? [While testing this, I just ran into a problem where I was running in the build directory. Insight added the breakpoints from .gdbinit to its list of installed breakpoints for the executable. Those buggers just coming out of the woodwork!] > Is there a possibility to tell insight not to ask ? Yes, you can add it to the ignored warnings list or teach insight that it is an ignorable warning (so it will only ask once). See gdbtk_tcl_warning in interface.tcl to globally ignore the warning. Unfortunately, teaching insight to optionally ignore the warning, i.e., "Don't show me this warning again", is slightly non-trivial (or at least more painful). GDB never did clean up the warning/error landscape. All we know is that it is a warning. Ignoring gdb, we'd have to add logic in place (similar to gdbtk_tcl_warning) to flag warnings are optionally ignorable. [Gdb just still doesn't get it.] Keith