This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] testsuite/boards/stabs.exp
- From: Doug Evans <xdje42 at gmail dot com>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: Yao Qi <yao at codesourcery dot com>, "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>
- Date: Sun, 14 Dec 2014 09:23:13 -0800
- Subject: Re: [PATCH] testsuite/boards/stabs.exp
- Authentication-results: sourceware.org; auth=none
- References: <m3d27ni060 dot fsf at seba dot sebabeach dot org> <87ioheviwk dot fsf at codesourcery dot com> <20141214132031 dot GQ5457 at adacore dot com>
On Sun, Dec 14, 2014 at 5:20 AM, Joel Brobecker <brobecker@adacore.com> wrote:
>> Alternatively, we can referencehttps://sourceware.org/gdb/wiki/TestingGDB ,
>> passing CFLAGS_FOR_TARGET='-gstabs' to dejagnu is convenient too, so I
>> don't see the necessity to add a new board file to do that.
>
> Another idea I thought about yesterday was to write a small python
> script that takes arguments on the command line and then calls make
> the right way for us, potentially even generating board files if
> necessary. The interesting bit in the script is the ability to call
> it with --help...
One nice thing about a board file for a specific purpose is that it's a place
to document issues related to that purpose.
And even add complexities related to that purpose.
Given that -g -gstabs != -gstabs -g,
I think we want to document that.
And also given that -gstabs != -gstabs -g,
we *may* (though I don't have as strong an opinion
on this as we're trying to kill^wstab stabs :-))
want a way to run stabs both ways.
E.g., bool.exp passes one way, and fails the other.
The stabs board file could be the repository
for "all things stabs".