From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1378 invoked by alias); 5 Jan 2011 20:53:50 -0000 Received: (qmail 1369 invoked by uid 22791); 5 Jan 2011 20:53:49 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from sibelius.xs4all.nl (HELO glazunov.sibelius.xs4all.nl) (83.163.83.176) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 05 Jan 2011 20:53:44 +0000 Received: from glazunov.sibelius.xs4all.nl (kettenis@localhost [127.0.0.1]) by glazunov.sibelius.xs4all.nl (8.14.3/8.14.3) with ESMTP id p05KrZT8014307; Wed, 5 Jan 2011 21:53:35 +0100 (CET) Received: (from kettenis@localhost) by glazunov.sibelius.xs4all.nl (8.14.3/8.14.3/Submit) id p05KrX6H003178; Wed, 5 Jan 2011 21:53:33 +0100 (CET) Date: Wed, 05 Jan 2011 20:53:00 -0000 Message-Id: <201101052053.p05KrX6H003178@glazunov.sibelius.xs4all.nl> From: Mark Kettenis To: tromey@redhat.com CC: gdb-patches@sourceware.org In-reply-to: (message from Tom Tromey on Wed, 05 Jan 2011 12:52:50 -0700) Subject: Re: RFA: document frame types, plus add missing ones References: 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: 2011-01/txt/msg00087.txt.bz2 > From: Tom Tromey > Date: Wed, 05 Jan 2011 12:52:50 -0700 > > This patch fixes PR python/12133. The bug is that the return values for > Frame.type are not documented. > > While doing this, I noticed that we didn't expose all the frame types. > So, this patch adds the missing ones as well. > > Doc review needed. > +@item gdb.INLINE_FRAME > +A frame representing an inlined function. The function was inlined > +into a @code{gdb.NORMAL_FRAME} that is newer than this one. It isn't quite clear to me what this last sentence means. > +@item gdb.SIGTRAMP_FRAME > +A frame in a signal handler. Hmm, actualy, the frame for what most people consider the signal handler is a NORMAL_FRAME. The SIGTRAMP_FRAME is the frame immediately preceding the signal handler. It is for the "signal trampoline", the bit of (low-level) code provided by the kernel or libc that runs the true signal handler. > +@item gdb.ARCH_FRAME > +A fake stack frame representing a cross-architecture call. Oh, we have those now? > +@item gdb.SENTINEL_FRAME > +This is like @code{gdb.NORMAL_FRAME}, but it is only used for the > +newest frame. Ah, so by "newest frame" you really mean "innermost frame".