This is the mail archive of the
mailing list for the GDB project.
RE: Mingw gdb validation
- From: "Pierre Muller" <muller at ics dot u-strasbg dot fr>
- To: "'Denis PILAT'" <denis dot pilat at st dot com>, "'gdb-patches'" <gdb-patches at sourceware dot org>
- Date: Wed, 22 Oct 2008 11:39:35 +0200
- Subject: RE: Mingw gdb validation
- References: <48FC4417.firstname.lastname@example.org>
I thought about this a while ago also,
and I was wondering if the best solution would not be to
have a global nl variable defined in gdb.exp
that would depend on the target you are testing.
I also thought at that time that we should
define two global variables: nl and nls.
"nl" as being something that is a single newline
defined generally as "\[\r\n\]" but probably as "\[\r\n\]\n?" for mingw32
"nls" if more than one newline is allowed and should generally be simply
Once these two variables are set in gdb.exp,
we should replace every "\[\r\n\]*" by a "$nls"
and all \[\r\n\]" by "$nl" in the expected answer part of the tests.
This should allow a lot of currently failing mingw32 test
It would also have the advantage of not changing
anything for other targets, unless we find other targets that
would benefit from a similar change, but that could then also
be inserted in gdb.exp special cases for nl and nls variables.
Nevertheless, changing all tests to use nl and nls
is probably not an easy task...
Pascal language support maintainer for GDB