From: Richard Earnshaw <rearnsha@arm.com>
To: gdb@sources.redhat.com
Cc: Richard.Earnshaw@arm.com
Subject: A brief analysis of the arm-elf failures for gdb
Date: Tue, 25 Mar 2003 16:48:00 -0000 [thread overview]
Message-ID: <200303251647.h2PGlxx13963@pc960.cambridge.arm.com> (raw)
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<int>
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<space>( 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.
next reply other threads:[~2003-03-25 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 16:48 Richard Earnshaw [this message]
2003-03-25 16:55 ` Corinna Vinschen
2003-03-25 16:55 ` Daniel Jacobowitz
2003-03-25 17:24 Michael Elizabeth Chastain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200303251647.h2PGlxx13963@pc960.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox