From: Daniel Jacobowitz <drow@false.org>
To: Michael Snyder <Michael.Snyder@palmsource.com>
Cc: Wu Zhou <woodzltc@cn.ibm.com>,
gdb@sourceware.org, Joel Brobecker <brobecker@adacore.com>,
Ramana Radhakrishnan <ramana.radhakrishnan@codito.com>
Subject: Re: a question about rs6k's prologue analysis
Date: Fri, 13 Oct 2006 22:03:00 -0000 [thread overview]
Message-ID: <20061013220321.GA25288@nevyn.them.org> (raw)
In-Reply-To: <1160766564.14535.263.camel@localhost.localdomain>
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
next prev parent reply other threads:[~2006-10-13 22:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 10:13 Wu Zhou
2006-10-11 10:47 ` Ramana Radhakrishnan
2006-10-11 13:53 ` Daniel Jacobowitz
2006-10-11 16:22 ` Joel Brobecker
2006-10-12 3:59 ` Wu Zhou
2006-10-13 4:13 ` Wu Zhou
2006-10-13 19:09 ` Michael Snyder
2006-10-13 22:03 ` Daniel Jacobowitz [this message]
2006-10-14 15:18 ` Wu Zhou
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061013220321.GA25288@nevyn.them.org \
--to=drow@false.org \
--cc=Michael.Snyder@palmsource.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=ramana.radhakrishnan@codito.com \
--cc=woodzltc@cn.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox