From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3172 invoked by alias); 25 Mar 2003 16:48:55 -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 3104 invoked from network); 25 Mar 2003 16:48:51 -0000 Received: from unknown (HELO fw-cam.cambridge.arm.com) (193.131.176.3) by sources.redhat.com with SMTP; 25 Mar 2003 16:48:51 -0000 Received: by fw-cam.cambridge.arm.com; id QAA24923; Tue, 25 Mar 2003 16:48:44 GMT Received: from unknown(172.16.1.2) by fw-cam.cambridge.arm.com via smap (V5.5) id xma024333; Tue, 25 Mar 03 16:47:59 GMT Received: from pc960.cambridge.arm.com (pc960.cambridge.arm.com [10.1.205.4]) by cam-admin0.cambridge.arm.com (8.9.3/8.9.3) with ESMTP id QAA12632; Tue, 25 Mar 2003 16:47:59 GMT Received: from pc960.cambridge.arm.com (rearnsha@localhost) by pc960.cambridge.arm.com (8.11.6/8.9.3) with ESMTP id h2PGlxx13963; Tue, 25 Mar 2003 16:47:59 GMT Message-Id: <200303251647.h2PGlxx13963@pc960.cambridge.arm.com> X-Authentication-Warning: pc960.cambridge.arm.com: rearnsha owned process doing -bs To: gdb@sources.redhat.com cc: Richard.Earnshaw@arm.com Reply-To: Richard.Earnshaw@arm.com Organization: ARM Ltd. X-Telephone: +44 1223 400569 (direct+voicemail), +44 1223 400400 (switchbd) X-Fax: +44 1223 400410 X-Address: ARM Ltd., 110 Fulbourn Road, Cherry Hinton, Cambridge CB1 9NJ. Subject: A brief analysis of the arm-elf failures for gdb Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 Mar 2003 16:48:00 -0000 From: Richard Earnshaw X-SW-Source: 2003-03/txt/msg00340.txt.bz2 Running the gdb testsuite on an arm-elf configuration and with current gcc shows just 20 failures. I've done a brief analysis of these below, it appears that most of the problems are related to the testsuite itself, rather than gdb. FAIL: gdb.base/args.exp: correct args printed FAIL: gdb.base/args.exp: correct args printed, one empty FAIL: gdb.base/args.exp: correct args printed, two empty These tests fail on a simulator because the framework omits the steps (gdb) target sim (gdb) load before trying to run the program. FAIL: gdb.base/huge.exp: print a very large data object This loads an application over the stack space. Consequently, when it runs the data area is clobbered by stack writes and we fail to get the desired output. Is there an easy way to disable this test? FAIL: gdb.base/ptype.exp: ptype t_char_array FAIL: gdb.base/ptype.exp: ptype func_type Neither of the above types are emitted in dwarf2 debug formats by gcc if they are not used. We need some data object with that type to make this test useful. FAIL: gdb.base/store.exp: next field 1 FAIL: gdb.base/store.exp: next field 2 FAIL: gdb.base/store.exp: next field 3 FAIL: gdb.base/store.exp: next field 4 The debugger is stopping on the line after the return statement (the closing brace for the function). If this is a bug at all, then it is most likely in gcc. FAIL: gdb.c++/anon-union.exp: print w 1 FAIL: gdb.c++/anon-union.exp: print z 1 FAIL: gdb.c++/anon-union.exp: print w 2 FAIL: gdb.c++/anon-union.exp: print z 2 FAIL: gdb.c++/anon-union.exp: print w 3 FAIL: gdb.c++/anon-union.exp: print z 3 Not sure what these are (c++). FAIL: gdb.c++/templates.exp: ptype T5 FAIL: gdb.c++/templates.exp: ptype t5i The information appears to differ only in white space from the "new with unsigned int" pattern. The pattern expects func( and gdb is emitting func(. FAIL: gdb.mi/mi-var-display.exp: get children local variable weird FAIL: gdb.mi/mi1-var-display.exp: get children local variable weird Don't know about these two. R.