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: Mingw gdb validation




Daniel Jacobowitz wrote:
On Mon, Oct 20, 2008 at 10:40:55AM +0200, Denis PILAT wrote:
Is there any chance for such a patch to be accepted ?
It allows the following test to be successful when using a MinGW gdb (means a gdb compiled under MSYS environment or using CFLAGS="-mno-cygwin" under cygwin).

That depends why it's necessary... we have been testing mingw GDB
binaries for at least a year, and I've never seen this failure.
Are you using a Cygwin expect binary to drive the GDB?
No I'm using ActiveState version of expect.
I didn't know it was possible to test non-cygwin GDBs in a cygwin environment. Each time I tried in the previous years, it fails.
Is there any specific stuff do apart from running runtest ?
If yes I will write a correct changelog entry.
The following $nl value is the only one that works both on linux and windows when running a validation.



About gdb.cp/userdef.exp, I don't understand why only in part of the tests we have a \r\n expected as the answer ?
gdb_test "print one % two" "\\\$\[0-9\]* = {x = 2, y = 3}"
gdb_test "print one && two" "\\\$\[0-9\]* = 1\[\r\n\]" <===== Why expecting \r\n here and not above ?

I don't know either, there it can probably be removed. It was
probably to ensure that there wasn't another character after the 1,
but gdb_test already does that.
Thanks, that's an explanation.
Denis


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