This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Fix parallel testing issues in gdb.guile tests

Doug Evans <> writes:

> Hmmm, there's something more going on here that we need to understand.
> [The patch may still be ok, but I'd still like to understand
> this error.]
> I don't see these fails.
> The files are going into $obj/gdb/testsuite/gdb.guile,
> which does exist.
> They *should* go in $obj/gdb/testsuite/outputs/foo, sure.
> But how come you're getting this error?

$obj/gdb/testsuite/gdb.guile doesn't exist in my setting.  I am hacking
gdb testsuite so that it can be run in a sub directory of 'testsuite/',
such as 'testsuite/sequential-tests', so that it can facilitate 'make clean'
('make clean' can only remove the directory 'sequential-tests').  That
is how this problem is exposed.

>> [...]
>> diff --git a/gdb/testsuite/gdb.guile/scm-section-script.exp
>> b/gdb/testsuite/gdb.guile/scm-section-script.exp
>> index 0c5e489..a1ebd10 100644
>> --- a/gdb/testsuite/gdb.guile/scm-section-script.exp
>> +++ b/gdb/testsuite/gdb.guile/scm-section-script.exp
>> @@ -35,14 +35,11 @@ standard_testfile
>>  # Make this available to gdb before the program starts, it is
>>  # automagically loaded by gdb.
>> -# Give the file a new name so we don't clobber the real one if
>> -# objfile == srcdir.
>>  # We also need to do this before compiling the program because the
>> name
>>  # of the script file is encoded in the binary.
>>  # FIXME: Can we get gdb_remote_download to call
>> standard_output_file for us?
> Please remove this FIXME while you're at it.

Sure, FIXME is removed.  I'll push it in.

Yao (éå)

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]