From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3140 invoked by alias); 10 Apr 2003 04:26:50 -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 3133 invoked from network); 10 Apr 2003 04:26:49 -0000 Received: from unknown (HELO zenia.red-bean.com) (12.222.151.100) by sources.redhat.com with SMTP; 10 Apr 2003 04:26:49 -0000 Received: from zenia.red-bean.com (localhost.localdomain [127.0.0.1]) by zenia.red-bean.com (8.12.5/8.12.5) with ESMTP id h3A4RYFq026372; Wed, 9 Apr 2003 23:27:35 -0500 Received: (from jimb@localhost) by zenia.red-bean.com (8.12.5/8.12.5/Submit) id h3A4RRD7026368; Wed, 9 Apr 2003 23:27:27 -0500 To: Daniel Jacobowitz CC: gdb@sources.redhat.com Subject: dwarf2read.c doesn't produce LOC_COMPUTED_ARG From: Jim Blandy Date: Thu, 10 Apr 2003 04:26:00 -0000 Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2.95 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-04/txt/msg00091.txt.bz2 I just realized that dwarf2read.c will produce LOC_COMPUTED symbols, but not LOC_COMPUTED_ARG symbols. The case for DW_TAG_formal_parameter in new_symbol doesn't call var_decode_location; it does what it's always done. Is there any reason for this, or was it just an oversight?