From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5852 invoked by alias); 18 Jul 2003 15:50:57 -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 5840 invoked from network); 18 Jul 2003 15:50:56 -0000 Received: from unknown (HELO localhost.redhat.com) (66.30.197.194) by sources.redhat.com with SMTP; 18 Jul 2003 15:50:56 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 833A42B7F; Fri, 18 Jul 2003 11:50:54 -0400 (EDT) Message-ID: <3F18175E.30607@redhat.com> Date: Fri, 18 Jul 2003 15:50:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Jacobowitz Cc: Elena Zannoni , gdb@sources.redhat.com, binutils@sources.redhat.com Subject: Re: What to do with info addr and location expressions References: <16152.3014.959070.885970@localhost.redhat.com> <20030718153016.GA17382@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-07/txt/msg00244.txt.bz2 [added binutils: gdb needs a way of printing out dwarf2 location expressions] > There are plenty of ways to fix it. In general, we need a location > expression pretty-printer - this is quite complicated, so no one's done > it yet. However, in specific, take a look at > locexpr_describe_location. You could just add another case which > recognizes the form GCC emits for thread-local variables to fix the > regression. > > Is that good enough? Why not share the readelf code? Print both the actual expression and (for simple cases) an english translation. Andrew