This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
RE: [RFA] ARI fix: Remove asprintf in breakpoint.c
With my change in gdb.base/sigstep.c
(and similar changes in gdb.base/sigXXX.c files)
and my change of gdb.exp to avoid interruption in
gdb.fortran/array-element.exp
I was able to complete a Cygwin testsuite in 45 minutes.
A lot better than previously.
I did not use Pedro's patch to fix the
i386_skip_prologue, thus the number of failures
are still huge.
Results are:
=== gdb Summary ===
# of expected passes 10186
# of unexpected failures 509
# of expected failures 59
# of known failures 30
# of unresolved testcases 38
# of untested testcases 8
# of unsupported tests 16
/usr/local/src/cvs/build/gdb/testsuite/../../gdb/gdb version
6.7.50-20071009-cvs -nx
gdb.pascal directory gives me just
a XFAIL for "Breakpoint 2" due to gpc problems with line information
and a KFAIL for "ptyp 'a single string'"
Thus I should be able to test my patches locally now...
Pierre Muller
Pasca language maintainer.
> -----Original Message-----
> From: gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] On Behalf Of Pierre Muller
> Sent: Tuesday, October 09, 2007 4:40 PM
> To: 'Pedro Alves'
> Cc: 'Joel Brobecker'; gdb-patches@sourceware.org
> Subject: RE: [RFA] ARI fix: Remove asprintf in breakpoint.c
>
> The main problem was
> gdb.base/sigstep.exp
> that took about 2 hours and 20 min to complete alone :(
> The main reason is that this is just a huge list of timeouts
> related to the fact that cygin only accepts
> ITIMER_REAL as first arg of setitimer.
> I will send a patch to fix this, by checking the return
> value of setitimer.
>
> Pierre
>
> > -----Original Message-----
> > From: Pedro Alves [mailto:alves.ped@gmail.com] On Behalf Of Pedro
> Alves
> > Sent: Monday, October 08, 2007 9:34 PM
> > To: Pierre Muller
> > Cc: 'Joel Brobecker'; gdb-patches@sourceware.org
> > Subject: Re: [RFA] ARI fix: Remove asprintf in breakpoint.c
> >
> > Pierre Muller wrote:
> > > No, sorry, but the testsuite on cygwin is really a pain,
> > > it has some signal problems that makes the testsuite
> > > horribly slow, with tons of timeouts...
> > > and no I have no easy linux access.
> > >
> >
> > I know what you mean ...
> >
> > I use these patches to be able to test on Cygwin less painfully:
> >
> > [PATCH] i386_skip_prologue
> > http://sources.redhat.com/ml/gdb-patches/2006-12/msg00140.html
> >
> > [[PATCH] Line info in the presence of __main, and
> > NOTE_INSN_FUNCTION_BEG after
> > scheduling:]
> > http://gcc.gnu.org/ml/gcc-patches/2006-12/msg00633.html
> >
> > The gcc patch is really outdated, and doesn't apply to
> > current gcc svn, so I still have a gcc build from 20061123
> > to test gdb. Far from ideal, but otherwise, many testcases timeout
> > and go untested.
> >
> > I keep wanting to fix this correctly, but I never get around to it.
> > From the last discussion on the subject, the idea was to teach the
> > i386 (and any other arch that cares) prologue reader about
> > __main as a first step. I don't think that's hard.
> >
> > Cheers,
> > Pedro Alves
> >
> >
>
>