From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30731 invoked by alias); 1 Oct 2003 14:49:08 -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 30693 invoked from network); 1 Oct 2003 14:49:07 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 1 Oct 2003 14:49:07 -0000 Received: from drow by nevyn.them.org with local (Exim 4.22 #1 (Debian)) id 1A4hj4-0000zs-US; Wed, 01 Oct 2003 10:13:10 -0400 Date: Wed, 01 Oct 2003 14:49:00 -0000 From: Daniel Jacobowitz To: ankit thukral Cc: gdb@sources.redhat.com Subject: Re: about class LOC_COMPUTED_ARG Message-ID: <20031001141310.GC3720@nevyn.them.org> Mail-Followup-To: ankit thukral , gdb@sources.redhat.com References: <20031001103543.22518.qmail@web60110.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031001103543.22518.qmail@web60110.mail.yahoo.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-10/txt/msg00025.txt.bz2 On Wed, Oct 01, 2003 at 03:35:43AM -0700, ankit thukral wrote: > hi all, > this is about the address class of the symbols > (arguments or local symbols) which is LOC_COMPUTED.for > this class , the value of the symbol is calculated by > calling some function called locexpr_read_variable() > which is stored in as a function pointer as against > the class LOC_BASEREG in which the location of the > symbols is calculated using the "base register + > offset" approach. > while debugging a process,i noticed that the argument > of some function had the address class LOC_BASEREG_ARG > while the same had LOC_COMPUTED_ARG in an older > version and newer version of GDB respectively.can > anyone tell me the reason for this shift i noticed? is > the class LOC_BASEREG_ARG becoming deprecated or is it > sort of buggy? > > > > thanks in advance, LOC_BASEREG_ARG was inadequate. LOC_COMPUTED_ARG is a more powerful mechanism, based on DWARF 2 location expressions. Take a look at http://www.eagercon.com/ if you want to find a copy of the specification. As I said in an earlier message, we don't have tracepoint support for LOC_COMPUTED or LOC_COMPUTED_ARG - yet. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer