From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11187 invoked by alias); 30 Jan 2004 05:27:43 -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 11178 invoked from network); 30 Jan 2004 05:27:43 -0000 Received: from unknown (HELO smtp10.atl.mindspring.net) (207.69.200.246) by sources.redhat.com with SMTP; 30 Jan 2004 05:27:43 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by smtp10.atl.mindspring.net with esmtp (Exim 3.33 #1) id 1AmRBv-0001cC-00 for gdb@sources.redhat.com; Fri, 30 Jan 2004 00:27:43 -0500 Received: by berman.michael-chastain.com (Postfix, from userid 502) id 301704B104; Fri, 30 Jan 2004 00:27:57 -0500 (EST) To: gdb@sources.redhat.com Subject: DW_OP_piece coming in gcc 3.4 Message-Id: <20040130052757.301704B104@berman.michael-chastain.com> Date: Fri, 30 Jan 2004 05:27:00 -0000 From: mec.gnu@mindspring.com (Michael Elizabeth Chastain) X-SW-Source: 2004-01/txt/msg00339.txt.bz2 I'm getting this with gcc-3_4-branch -gdwarf-2: (gdb) PASS: gdb.base/store.exp: up print old l - longest print r^M Unhandled dwarf expression opcode 0x93^M (gdb) FAIL: gdb.base/store.exp: up print old r - longest We need a strategic decision: (1) Implement DW_OP_piece in time for gdb 6.1. (2) Ask gcc to not emit DW_OP_piece in gcc 3.4. (3) File a PR (or tag onto PR gdb/1312 but that's not really right), KFAIL the tests, add a note to PROBLEMS. I don't know which strategy is good for gdb. What will it be? Michael C