This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: RFA: ia64 portion of libunwind patch
- From: David Mosberger <davidm at napali dot hpl dot hp dot com>
- To: Marcel Moolenaar <marcel at xcllnt dot net>
- Cc: "J. Johnston" <jjohnstn at redhat dot com>,gdb-patches at sources dot redhat dot com, Andrew Cagney <ac131313 at redhat dot com>,Kevin Buettner <kevinb at redhat dot com>, davidm at hpl dot hp dot com
- Date: Fri, 31 Oct 2003 15:00:32 -0800
- Subject: Re: RFA: ia64 portion of libunwind patch
- References: <3FA2B71A.3080905@redhat.com><20031031213551.GA67387@dhcp01.pn.xcllnt.net>
- Reply-to: davidm at hpl dot hp dot com
>>>>> On Fri, 31 Oct 2003 13:35:51 -0800, Marcel Moolenaar <marcel@xcllnt.net> 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