Re: a question about rs6k's prologue analysis

Daniel Jacobowitz
2006-10-13T22:03:35Z

On Fri, Oct 13, 2006 at 12:09:24PM -0700, Michael Snyder wrote:
> On Fri, 2006-10-13 at 12:13 +0800, Wu Zhou wrote:
>
> > < ERROR: internal buffer is full.
> > < UNRESOLVED: gdb.base/checkpoint.exp: info checkpoints with at least 600 checkpoints
> > ---
> > > PASS: gdb.base/checkpoint.exp: info checkpoints with at least 600 checkpoints
> >
> > *** Patched gdb have an internal buffer full error, which make checkpoint.exp have a unresolved case.
>
> Could you run the checkpoint.exp test by itself, and post the
> relevant portion of the gdb.log file?
>
>
> >
> > 11453a11453
> > > PASS: gdb.threads/schedlock.exp: other thread 0 didn't run
> > 11455d11454
> > < PASS: gdb.threads/schedlock.exp: other thread 1 didn't run
> > 11472a11472
> > > PASS: gdb.threads/schedlock.exp: other thread 0 didn't run (stepping)
> > 11474d11473
> > < PASS: gdb.threads/schedlock.exp: other thread 1 didn't run (stepping)
> >
> > *** patched gdb has two PASSes which occur at different thread.
>
> Could you also run this test by itself and post the gdb.log?

All of these tests are timing sensitive. I don't know why for
checkpoint.exp - that one can probably be fixed. For schedlock, I
think we ought to weaken the tests somewhat; right now, it's very
sensitive to load on the test machine.

--
Daniel Jacobowitz
CodeSourcery