From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17473 invoked by alias); 27 Jun 2014 15:25:08 -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 17360 invoked by uid 89); 27 Jun 2014 15:25:07 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.8 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Fri, 27 Jun 2014 15:25:06 +0000 Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s5RFP3kc022012 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 27 Jun 2014 11:25:04 -0400 Received: from localhost.localdomain (ovpn-112-22.ams2.redhat.com [10.36.112.22]) by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s5RFP2h7009194; Fri, 27 Jun 2014 11:25:03 -0400 Message-ID: <53AD8CCE.6050500@redhat.com> Date: Fri, 27 Jun 2014 15:25:00 -0000 From: Phil Muldoon MIME-Version: 1.0 To: Aleksey Midenkov CC: gdb@sourceware.org Subject: Re: gobject.pyc: gdb was not built with custom backtrace support, disabling. References: <53AD7BDF.3020909@redhat.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2014-06/txt/msg00094.txt.bz2 On 27/06/14 16:18, Aleksey Midenkov wrote: > On Fri, Jun 27, 2014 at 6:12 PM, Phil Muldoon wrote: >> On 27/06/14 14:19, Aleksey Midenkov wrote: >>> Hi! >>> >>> This message comes from /usr/share/glib-2.0/gdb/gobject.py. How this >>> path is included into gdb? I want to remove it from processing. >> >> This is coming from the frame filter installed with that >> package. Ideally a frame filter should print nothing if it cannot >> process a stack-frame. You can remove it permanently from processing >> by uninstalling the package that installs the frame filter (in Fedora's >> case, that is glib-devel I think). >> >> Alternatively you can use the "disable frame-filter" command in GDB. >> > > Do I have third option? I don't want to uninstall glib-devel and don't > want to disable frame-filter. Can I exclude '/usr/share/glib-2.0/gdb' > from processing? How GDB collects info on frame filters anyway? Do > they register somewhere? Frame filters, pretty printers etc all self register via auto loading. In Fedora the auto-loading location is: /usr/share/gdb/auto-load/ You will find the auto-load scripts for glib and others there. You have many options, but this is not strictly a GDB issue so I can only advise: 1) File a bug with glib noting the error message is distracting and serves no purpose. 2) Edit the py file to delete the print. 3) Start GDB with gdb -ex "disable frame-filters all" 4) Edit the glib auto load files not to register the frame filter. Cheers Phil