This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: Problems with dejagnu and c++ tests...
- From: mec dot gnu at mindspring dot com (Michael Elizabeth Chastain)
- To: cagney at gnu dot org, mec dot gnu at mindspring dot com
- Cc: brobecker at gnat dot com, gdb-patches at sources dot redhat dot com
- Date: Wed, 4 Feb 2004 18:03:42 -0500 (EST)
- Subject: Re: Problems with dejagnu and c++ tests...
> Which would mean that a GCC code-gen bug in malloc, or printf would
> block all ability to run the testsuite :-(
Ah, I see.
So don't use printf ... use write(2).
There are 310 *.exp files in the test suite.
84 of them use get_compiler_info.
47 of them actually use one of the tests:
test_compiler_info
gcc_compiled, hp_aCC_compiler, hp_cc_compiler
signed_keyword_not_used
(Hmmm, I feel an obvious change coming to 37 files).
84 out of 310 is not even close to "all".
If I did the compiler checks up front instead of inside get_compiler_info,
then the compiler checks would have to do something nice if
gdb_compile failed, such as leave compiler_info set to "no-compiler"
for the language that failed.
Michael C