From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13601 invoked by alias); 27 Jun 2014 15:19:03 -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 13585 invoked by uid 89); 27 Jun 2014 15:19:03 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-oa0-f45.google.com Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Fri, 27 Jun 2014 15:18:56 +0000 Received: by mail-oa0-f45.google.com with SMTP id o6so5858845oag.32 for ; Fri, 27 Jun 2014 08:18:54 -0700 (PDT) X-Received: by 10.60.142.169 with SMTP id rx9mr24047401oeb.1.1403882334331; Fri, 27 Jun 2014 08:18:54 -0700 (PDT) MIME-Version: 1.0 Received: by 10.182.66.116 with HTTP; Fri, 27 Jun 2014 08:18:34 -0700 (PDT) In-Reply-To: <53AD7BDF.3020909@redhat.com> References: <53AD7BDF.3020909@redhat.com> From: Aleksey Midenkov Date: Fri, 27 Jun 2014 15:19:00 -0000 Message-ID: Subject: Re: gobject.pyc: gdb was not built with custom backtrace support, disabling. To: Phil Muldoon Cc: gdb@sourceware.org Content-Type: text/plain; charset=UTF-8 X-SW-Source: 2014-06/txt/msg00093.txt.bz2 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?