From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3595 invoked by alias); 17 Jan 2007 22:17:59 -0000 Received: (qmail 3587 invoked by uid 22791); 17 Jan 2007 22:17:58 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Wed, 17 Jan 2007 22:17:51 +0000 Received: from drow by nevyn.them.org with local (Exim 4.63) (envelope-from ) id 1H7J6E-0003x6-FF; Wed, 17 Jan 2007 17:17:42 -0500 Date: Wed, 17 Jan 2007 22:17:00 -0000 From: Daniel Jacobowitz To: =?iso-8859-1?Q?Fr=E9d=E9ric?= Riss Cc: Vladimir Prus , gdb-patches@sources.redhat.com Subject: Re: [RFC] Prints the frame id when target stops Message-ID: <20070117221742.GA15116@nevyn.them.org> Mail-Followup-To: =?iso-8859-1?Q?Fr=E9d=E9ric?= Riss , Vladimir Prus , gdb-patches@sources.redhat.com References: <45AB9A7F.1090502@st.com> <17837.16328.46414.146270@kahikatea.snap.net.nz> <200701170234.34303.ghost@cs.msu.su> <200701172128.l0HLSOTc024176@brahms.sibelius.xs4all.nl> <1169071153.5155.71.camel@funkylaptop> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1169071153.5155.71.camel@funkylaptop> User-Agent: Mutt/1.5.13 (2006-08-11) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2007-01/txt/msg00394.txt.bz2 On Wed, Jan 17, 2007 at 10:59:13PM +0100, Frédéric Riss wrote: > Have you an idea how you would like the caching to work? Do you mean not > discarding the frame cache, or caching the returned string? How much do we know about why it takes a long time? For instance: - We can speed up the psymtab lookup which currently shows up in profiles. A coworker of mine gave me some clever ideas on how to do this if anyone wants to try it :-) - We can speed up prologue analyzers by judicious use of caching, in a way that's completely reliable. DWARF2 CFI is already pretty speedy. If these sorts of things are enough to help... > Also, I don't see how we could have better checks within GDB than within > the frontend. The only reliable check is IMHO to compare frame ids after > steps and nexts. I suspect you can only do this in stepi, really - step/next can end up in strange places... -- Daniel Jacobowitz CodeSourcery