This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v2 11/17] introduce relative_filename and use it
- From: Tom Tromey <tromey at redhat dot com>
- To: Pedro Alves <palves at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Fri, 25 Oct 2013 10:42:51 -0600
- Subject: Re: [PATCH v2 11/17] introduce relative_filename and use it
- Authentication-results: sourceware.org; auth=none
- References: <1382129374-18344-1-git-send-email-tromey at redhat dot com> <1382129374-18344-12-git-send-email-tromey at redhat dot com> <526A9AA4 dot 1040304 at redhat dot com>
>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
Pedro> On 10/18/2013 09:49 PM, Tom Tromey wrote:
>> This introduces a new relative_filename proc to gdb.exp and changes
>> some tests to use it. This helps make these tests parallel-safe.
>>
>> * gdb.base/fullname.exp: Use standard_output_file,
>> relative_filename.
>> * gdb.base/hashline1.exp: Use standard_testfile,
>> standard_output_file, relative_filename, clean_restart.
>> * gdb.base/hashline2.exp: Use standard_testfile,
>> standard_output_file, relative_filename.
>> * gdb.base/hashline3.exp: Use standard_testfile,
>> standard_output_file, relative_filename.
>> * lib/gdb.exp (relative_filename): New proc.
Pedro> It seems like gdb.base/hashline2.exp doesn't actually use
Pedro> relative_filename. Was that a mistake?
I looked, and it was intentional.
The test case is supposed to use absolute file names here.
I've corrected the ChangeLog entry.
Tom