From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29137 invoked by alias); 19 Mar 2010 15:07:03 -0000 Received: (qmail 29103 invoked by uid 22791); 19 Mar 2010 15:06:59 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 19 Mar 2010 15:06:49 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 02BAC2BABAD; Fri, 19 Mar 2010 11:06:48 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id COYk6b8rh6y8; Fri, 19 Mar 2010 11:06:47 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id C7F302BABAC; Fri, 19 Mar 2010 11:06:47 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id B21A0F593B; Fri, 19 Mar 2010 08:06:44 -0700 (PDT) Date: Fri, 19 Mar 2010 15:07:00 -0000 From: Joel Brobecker To: Asm_gmail Cc: gdb@sourceware.org Subject: Re: gdb-7.1 - last call before release (Wed, Mar 17th) Message-ID: <20100319150644.GI2858@adacore.com> References: <20100316161124.GE3844@adacore.com> <4BA03709.6070702@gmail.com> <20100317141208.GJ3844@adacore.com> <4BA2DD0A.9030904@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4BA2DD0A.9030904@gmail.com> User-Agent: Mutt/1.5.20 (2009-06-14) 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: 2010-03/txt/msg00171.txt.bz2 I'm not familiar with C++ debugging, so there is not much I can do in this case to help. The fact that it returns very quickly when the variable is in scope seems logical - I would imagine that symbol lookups by name search the current scope first, before expanding the search to the global scope. As for the search in the global scope, it's hard to say... Perhaps if you create a PR and provide a reproducer, someone will be able to find out more. -- Joel