From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13694 invoked by alias); 14 Sep 2004 15:39:13 -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 13687 invoked from network); 14 Sep 2004 15:39:13 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 14 Sep 2004 15:39:13 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.10) with ESMTP id i8EFdCpL005507 for ; Tue, 14 Sep 2004 11:39:12 -0400 Received: from zenia.home.redhat.com (porkchop.devel.redhat.com [172.16.58.2]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i8EFdBr02563; Tue, 14 Sep 2004 11:39:12 -0400 To: gdb@sources.redhat.com Subject: implementing full scattered values From: Jim Blandy Date: Tue, 14 Sep 2004 15:39:00 -0000 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: 2004-09/txt/msg00100.txt.bz2 Last month there was a thread on supporting DW_OP_piece: http://sources.redhat.com/ml/gdb/2004-08/msg00004.html Everyone agreed that having architecture-independent support for arbitrary DW_OP_piece location expressions would be preferable to the partial and architecture-dependent support, if someone could find time to do it soon. Let's talk about full scattered value support. What's the best approach? What's entailed? How do we want 'struct value' to look when we're done? Let's try to set some concrete goals so that if someone does have the cycles to work on this, they can have some idea what to work towards so it'll be acceptable for inclusion in the public sources.