From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28533 invoked by alias); 9 May 2005 05:30:12 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 28524 invoked by uid 22791); 9 May 2005 05:30:09 -0000 Received: from mail-out3.apple.com (HELO mail-out3.apple.com) (17.254.13.22) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 09 May 2005 05:30:09 +0000 Received: from mailgate2.apple.com (a17-128-100-204.apple.com [17.128.100.204]) by mail-out3.apple.com (8.12.11/8.12.11) with ESMTP id j495U7dF021152 for ; Sun, 8 May 2005 22:30:07 -0700 (PDT) Received: from relay2.apple.com (relay2.apple.com) by mailgate2.apple.com (Content Technologies SMTPRS 4.3.17) with ESMTP id ; Sun, 8 May 2005 22:30:07 -0700 Received: from [17.219.205.66] ([17.219.205.66]) by relay2.apple.com (8.12.11/8.12.11) with ESMTP id j495U45S001423; Sun, 8 May 2005 22:30:04 -0700 (PDT) Message-ID: <427EF55B.8090503@apple.com> Date: Mon, 09 May 2005 05:30:00 -0000 From: Stan Shebs User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.3) Gecko/20040910 MIME-Version: 1.0 To: Christopher Faylor CC: roland.schwingel@onevision.de, gdb@sourceware.org Subject: Re: gdb stack trace problems (Addendum) References: <4275D0AC.8000205@onevision.de> <200505081330.j48DUKQc012365@elgar.sibelius.xs4all.nl> <20050508231953.GG3896@trixie.casa.cgf.cx> In-Reply-To: <20050508231953.GG3896@trixie.casa.cgf.cx> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-05/txt/msg00102.txt.bz2 Christopher Faylor wrote: > >If a function doesn't set up a frame pointer and there is no debugging >information available, how would one derive a stack frame? I could >imagine a really complicated "search the stack" technique but I can't >see how it would ever be foolproof. > That's where GDB hacking just starts to get interesting. :-) Yes, it's complicated and potentially expensive too, because you may have to transfer a lot of bytes. The mips has something similar for function starts, and a "heuristic-fence-post" variable to control how hard to work at it. Stan