From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11343 invoked by alias); 31 Oct 2003 23:00:38 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 11336 invoked from network); 31 Oct 2003 23:00:38 -0000 Received: from unknown (HELO palrel13.hp.com) (156.153.255.238) by sources.redhat.com with SMTP; 31 Oct 2003 23:00:38 -0000 Received: from hplms2.hpl.hp.com (hplms2.hpl.hp.com [15.0.152.33]) by palrel13.hp.com (Postfix) with ESMTP id 646B71C01C8C; Fri, 31 Oct 2003 15:00:37 -0800 (PST) Received: from napali.hpl.hp.com (napali.hpl.hp.com [15.4.89.123]) by hplms2.hpl.hp.com (8.12.10/8.12.10/HPL-PA Hub) with ESMTP id h9VN0aRU003729; Fri, 31 Oct 2003 15:00:36 -0800 (PST) Received: from napali.hpl.hp.com (napali [127.0.0.1]) by napali.hpl.hp.com (8.12.3/8.12.3/Debian-6.6) with ESMTP id h9VN0aFO010603; Fri, 31 Oct 2003 15:00:36 -0800 Received: (from davidm@localhost) by napali.hpl.hp.com (8.12.3/8.12.3/Debian-6.6) id h9VN0W6l010599; Fri, 31 Oct 2003 15:00:32 -0800 From: David Mosberger MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16290.59792.76966.437973@napali.hpl.hp.com> Date: Fri, 31 Oct 2003 23:00:00 -0000 To: Marcel Moolenaar Cc: "J. Johnston" , gdb-patches@sources.redhat.com, Andrew Cagney , Kevin Buettner , davidm@hpl.hp.com Subject: Re: RFA: ia64 portion of libunwind patch In-Reply-To: <20031031213551.GA67387@dhcp01.pn.xcllnt.net> References: <3FA2B71A.3080905@redhat.com> <20031031213551.GA67387@dhcp01.pn.xcllnt.net> Reply-To: davidm@hpl.hp.com X-URL: http://www.hpl.hp.com/personal/David_Mosberger/ X-SW-Source: 2003-10/txt/msg00897.txt.bz2 >>>>> On Fri, 31 Oct 2003 13:35:51 -0800, Marcel Moolenaar said: Marcel> Since libunwind already does its own caching, we may be Marcel> better off not caching in gdb. That's true. However, note that by default, caching is not enabled for remote unwinding (which is what gdb does). To enable caching, gdb would have to make a call of the form: unw_set_caching_policy(ADDR_SPACE, UNW_CACHE_GLOBAL); Also, whenever something changes in the target that could invalidate cached unwind info, gdb would have to call: unw_flush_cache(ADDR_SPACE, LO, HI); where LO and HI is the address range that was affected (or LO=0, HI=0 to flush the entire cache). --david