This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [commit] gdb.python/py-evthreads.exp regression [Re: [PATCH] Handle multiple breakpoint hits in Python interface]
On Fri, Sep 16, 2011 at 9:35 AM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
>
> On Thu, 15 Sep 2011 14:30:21 +0200, Kevin Pouget wrote:
> > commited
> >
> > http://sourceware.org/ml/gdb-cvs/2011-09/msg00085.html
>
> Regressed:
> FAIL: gdb.python/py-evthreads.exp: Run to breakpoint 1
> FAIL: gdb.python/py-evthreads.exp: reached breakpoint 2
> FAIL: gdb.python/py-evthreads.exp: reached breakpoint 3
>
> ?event type: stop
> ?event type: stop
> ?stop reason: breakpoint
> +first breakpoint number: 1
> ?breakpoint number: 1
> ?thread num: 1
> -(gdb) PASS: gdb.python/py-evthreads.exp: Run to breakpoint 1
> +(gdb) FAIL: gdb.python/py-evthreads.exp: Run to breakpoint 1
>
> I understand gdb.python/py-evthreads.exp has been checked in between your
> patch development and its check-in.
>
> Checked in.
>
>
> Regards,
> Jan
Thanks for noticing that, Jan, next time I'll double-check that there
is no regression at commit time, and not only when the patch is being
validated
Cordially,
Kevin