This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: FAILs on x86?
On Thursday 27 March 2008 16:28:51 Markus Deuling wrote:
> Vladimir Prus schrieb:
> > On Thursday 27 March 2008 15:33:08 Markus Deuling wrote:
> >> Vladimir Prus schrieb:
> >>> Markus Deuling wrote:
> >>>
> >>>> Daniel Jacobowitz schrieb:
> >>>>> On Thu, Mar 27, 2008 at 12:37:03PM +0100, Markus Deuling wrote:
> >>>>>> Hi,
> >>>>>>
> >>>>>> I see lots of FAILs on x86. Anyone else seeing this?
> >>>>> Not me. What's in gdb.log for a typical failure?
> >>>>>
> >>>> Nothing special, I think (I dont think its an environment problem). Just a lot of FAILs in
> >>>> gdb.{base,cp,mi}. I posted a list of the FAILs that are new compared to a testrun some days ago
> >>>> here:
> >>>>
> >>>> http://sourceware.org/ml/gdb-testers/2008-q1/msg00022.html
> >>>>
> >>>> As far as I see there were some commits to some areas where GDB test fails
> >>>> now (gdb.cp, gdb.mi, dfp). If needed I can attach gdb.log
> >>> When were the tests run? gdb.mi failures are supposed to be fixed now.
> >>>
> >>> - Volodya
> >>>
> >> Today, just an hour ago. I currently re-run tests for ppc and spu.
> >>
> >
> > Strange. Does testsuite/Changelog have the following:
> >
> > 2008-03-26 Vladimir Prus <vladimir@codesourcery.com>
> >
> > * lib/mi-support.exp (mi_create_varobj_checked): New.
> > (mi_list_varobj_children): Allow to check for a
> > value.
> > (mi_list_array_varobj_children): New.
> >
> > * gdb.mi/mi-var-child.exp: Use mi_create_varobj
> > and mi_list_varobj_children, as opposed to hardcoding
> > expected strings.
> > * gdb.mi/gdb701.exp: Likewise.
> > * gdb.mi/gdb792.exp: Likewise.
> > * gdb.mi/mi-var-block.exp: Likewise.
> > * gdb.mi/mi-var-cmd.exp: Likewise.
> > * gdb.mi/mi-var-invalidate.exp: Likewise.
> > * gdb.mi/mi2-var-block.exp: Likewise.
> > * gdb.mi/mi2-var-child.exp: Likewise.
> > * gdb.mi/mi2-var-cmd.exp: Likewise.
> > * gdb.mi/mi2-var-display.exp: Likewise.
> >
> > ?
> >
> > - Volodya
> >
> >
>
> Yes, I test against current head.
Then, I need gdb.log part for the first failure, namely this:
FAIL: gdb.mi/gdb701.exp: create fooPtr
- Volodya