This is the mail archive of the gdb-patches@sourceware.org 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: GDB version as convenience variable


> Date: Tue, 26 Mar 2019 13:57:16 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
> 
> This is going to be one more manual test to do after each branch,
> and I'm a bit concerned about that. We can start with that, as we want
> the test to pass. But I'm wondering if, instead of getting the output
> from "show version" to determine the expected values, we could parse
> gdb/version.in instead. If needed, we could so the parsing as part of
> the build process (ig do it in the makefile, and store the result in
> a couple of files). Something like that.

Yes, if version.in is updated by some automated method, the same
method could update the test suite.


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