From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1694 invoked by alias); 27 Jul 2007 05:57:33 -0000 Received: (qmail 1681 invoked by uid 22791); 27 Jul 2007 05:57:33 -0000 X-Spam-Check-By: sourceware.org Received: from smtp103.biz.mail.mud.yahoo.com (HELO smtp103.biz.mail.mud.yahoo.com) (68.142.200.238) by sourceware.org (qpsmtpd/0.31) with SMTP; Fri, 27 Jul 2007 05:57:28 +0000 Received: (qmail 2503 invoked from network); 27 Jul 2007 05:57:27 -0000 Received: from unknown (HELO ?192.168.1.100?) (wenbo.yang@simplnano.com@211.101.21.42 with plain) by smtp103.biz.mail.mud.yahoo.com with SMTP; 27 Jul 2007 05:57:25 -0000 X-YMail-OSG: ZJTu2XQVM1lfwHQ4q6VWbWx.wtpaq6fiF_i5kpToQJVyNCgn207g23dkj5BDatlcpYaMP2y1GKSiohTxQQJRwkFKpg-- Message-ID: <46A98934.5040902@simplnano.com> Date: Fri, 27 Jul 2007 09:18:00 -0000 From: Wenbo Yang User-Agent: Thunderbird 2.0.0.4 (X11/20070625) MIME-Version: 1.0 To: Michael Eager CC: Mark Kettenis , gdb@sources.redhat.com Subject: Re: frame cache References: <46A648BC.8070105@eagercon.com> In-Reply-To: <46A648BC.8070105@eagercon.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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 X-SW-Source: 2007-07/txt/msg00188.txt.bz2 Michael Eager wrote: > Perhaps so, I don't see where other targets check for debug > info before calling analyze_prologue(). For example, on i386, > i386_analyze_prologue() is called each and every time that > i386_skip_prologue() is called. It depends on target . If you register dwarf2 frame sniffers to gdbarch, and your compiler can emit proper debugging information, gdb will not call analyze_prologue(). At least for our target(I did the porting), it works as Mark Kettenis said: "prologue analysis should only be done as a last resort, i.e. when proper debug information is not available. " > I don't see where there is any test in symtab.c or infrun.c > which tests for debug info before calling SKIP_PROLOGUE which > calls _skip_prologue. Because if you want to use debugging information to skip prologue, you write the code in this function. So, test should be place here in this function. Wenbo -- Wenbo Yang The State Key Lab. of Information Security Graduate School of CAS, 19A Yuquan Road, Beijing, China Homepage: http://solrex.cn SimpLight Nanoelectronics Ltd. 6 Zhichun Road, 10th Floor, Beijing, China Phone: +86-10-5126-6989 --- Email: wenbo.yang@simplnano.com