From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9929 invoked by alias); 21 Nov 2011 21:50:17 -0000 Received: (qmail 9916 invoked by uid 22791); 21 Nov 2011 21:50:15 -0000 X-SWARE-Spam-Status: No, hits=-7.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 21 Nov 2011 21:49:40 +0000 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id pALLnbPM005652 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 21 Nov 2011 16:49:37 -0500 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id pALLnaO2029845; Mon, 21 Nov 2011 16:49:36 -0500 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id pALLnYTs005942; Mon, 21 Nov 2011 16:49:35 -0500 From: Tom Tromey To: Yao Qi Cc: Jan Kratochvil , gdb-patches@sourceware.org Subject: Re: RFA: implement ambiguous linespec proposal References: <20111028221459.GA28467@host1.jankratochvil.net> <20111104074543.GA13839@host1.jankratochvil.net> <4EC3DA13.4060907@codesourcery.com> <4EC48425.2040407@codesourcery.com> Date: Mon, 21 Nov 2011 21:50:00 -0000 In-Reply-To: <4EC48425.2040407@codesourcery.com> (Yao Qi's message of "Thu, 17 Nov 2011 11:48:53 +0800") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.90 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain 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-11/txt/msg00548.txt.bz2 >>>>> "Yao" == Yao Qi writes: >> (top-gdb) p *sym.symtab Yao> OOC, could you give me a stack backtrace here? Sorry, the session is long gone. Basically I stopped in parse_exp_1, continued until for the parsing happened for the "bad" location, then stepped through lookup_symbol_in_language to see how gdb was resolving 'a'. Tom