From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27599 invoked by alias); 25 Apr 2012 20:56:28 -0000 Received: (qmail 27590 invoked by uid 22791); 25 Apr 2012 20:56:27 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout21.012.net.il (HELO mtaout21.012.net.il) (80.179.55.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 25 Apr 2012 20:56:13 +0000 Received: from conversion-daemon.a-mtaout21.012.net.il by a-mtaout21.012.net.il (HyperSendmail v2007.08) id <0M3100A00ZCPU500@a-mtaout21.012.net.il> for gdb-patches@sourceware.org; Wed, 25 Apr 2012 23:56:11 +0300 (IDT) Received: from HOME-C4E4A596F7 ([84.229.249.186]) by a-mtaout21.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0M3100A5UZHMSQ40@a-mtaout21.012.net.il>; Wed, 25 Apr 2012 23:56:11 +0300 (IDT) Date: Wed, 25 Apr 2012 21:02:00 -0000 From: Eli Zaretskii Subject: Re: [RFC - doc] Add note about the possibility of symbols getting moved across blocks In-reply-to: <87ipgna94k.fsf@fleche.redhat.com> To: Tom Tromey Cc: sivachandra@google.com, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83y5pjedjp.fsf@gnu.org> References: <83bomgfcbt.fsf@gnu.org> <87ipgna94k.fsf@fleche.redhat.com> 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: 2012-04/txt/msg00890.txt.bz2 > From: Tom Tromey > Cc: Siva Chandra , gdb-patches@sourceware.org > Date: Wed, 25 Apr 2012 13:45:15 -0600 > > >> A @code{gdb.Block} is iterable. The iterator returns the symbols > >> -(@pxref{Symbols In Python}) local to the block. > >> +(@pxref{Symbols In Python}) local to the block. Users using this > >> +feature should keep in mind that future improvements to the internal > >> +representation, of symbols and symbol tables, can move symbols across > >> +blocks within a symbol table. > > Eli> Thanks. But I still don't see how the warning is useful. What should > Eli> I do or not do if I want to avoid whatever dangers you warn me about? > > You could test new versions of gdb to be sure they conform to your > expectations. I meant what should I do or not do as the user of the Python API in question. Or maybe I misunderstand what you are saying, sorry.