From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26277 invoked by alias); 2 Oct 2003 03:52:26 -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 26268 invoked from network); 2 Oct 2003 03:52:25 -0000 Received: from unknown (HELO zenia.home) (12.223.225.216) by sources.redhat.com with SMTP; 2 Oct 2003 03:52:25 -0000 Received: by zenia.home (Postfix, from userid 5433) id 1CCD520766; Wed, 1 Oct 2003 22:47:59 -0500 (EST) To: ankit thukral Cc: Daniel Jacobowitz , gdb@sources.redhat.com Subject: Re: about class LOC_COMPUTED_ARG References: <20031001103543.22518.qmail@web60110.mail.yahoo.com> <20031001141310.GC3720@nevyn.them.org> From: Jim Blandy Date: Thu, 02 Oct 2003 03:52:00 -0000 In-Reply-To: <20031001141310.GC3720@nevyn.them.org> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-10/txt/msg00046.txt.bz2 Daniel Jacobowitz writes: > 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. As a workaround until that's done, you might try compiling with -gstabs+. Only the Dwarf 2 reader generates LOC_COMPUTED and LOC_COMPUTED_ARG; the stabs reader will generate LOC_BASEREG_ARG and stuff like that, which ax-gdb.c knows how to handle.