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: [RFC] Check setitimer return value in testsuite/gdb.base/sigstep.c

From: "Pierre Muller" <muller at ics dot u-strasbg dot fr>
To: "'Daniel Jacobowitz'" <drow at false dot org>
Cc: <gdb-patches at sourceware dot org>
Date: Mon, 15 Oct 2007 11:23:14 +0200
Subject: RE: [RFC] Check setitimer return value in testsuite/gdb.base/sigstep.c
References: <003201c80a85$df280850$9d7818f0$@u-strasbg.fr> <20071011191436.GD30810@caradoc.them.org>

> 
> itimer =, not itime =.
> 
> Otherwise OK.  Thanks!
> 
> --
> Daniel Jacobowitz
> CodeSourcery

Thanks, I check the change in, taking your correction.

Pierre Muller

Thus running on cygwin:

Running 'make check RUNTESTFLAGS=gdb.base/sigstep.exp'
New version result:

                === gdb Summary ===

# of expected passes            63
# of unexpected failures        50
# of known failures             6
/usr/local/src/cvs/build/gdb/testsuite/../../gdb/gdb version
6.7.50-20071015-cvs -nx

Takes approximatively 40 seconds.

Old version result:

                === gdb Summary ===

# of expected passes            2
# of unexpected failures        110
# of known failures             6
# of unresolved testcases       1
/usr/local/src/cvs/build/gdb/testsuite/../../gdb/gdb version
6.7.50-20071015-cvs -nx


took approximatively 2 hours.

  The remaining failures are due, at least partly
to signal handling problems. Which occur all over
cygwin testsuite.

Pierre Muller

References:
- [RFC] Check setitimer return value in testsuite/gdb.base/sigstep.c
  - From: Pierre Muller
- Re: [RFC] Check setitimer return value in testsuite/gdb.base/sigstep.c
  - From: Daniel Jacobowitz

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