This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] gdb.python: Do all C testing before any C++ testing.
- From: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- To: Doug Evans <dje at google dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Tue, 15 May 2012 16:26:29 +0200
- Subject: Re: [patch] gdb.python: Do all C testing before any C++ testing.
- References: <20120515053556.3F97B2461B0@ruffy.mtv.corp.google.com>
On Tue, 15 May 2012 07:35:56 +0200, Doug Evans wrote:
> One of the properties of Fission is that the output of the compiler
> is now two files: foo.o and foo.dwo.
>
> So if we compile foo.c as C and then as C++, the C++ compile
> will clobber the C foo.dwo and the tests will fail.
This violates the rule failures should be reproducible by hand after the
testfile has finished. Currently in many cases one has to patch out parts of
the .exp file when investigating a FAIL case. I do not find great to do it
intentionally and for multiple files.
lib/gdb.exp should be changed or at least the testfile should compile each
{object} file itself with unique name so that the files are not clobbered.
Thanks,
Jan