Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA (threads testsuite): More thread tests
Date: Thu, 22 Aug 2002 18:35:00 -0000	[thread overview]
Message-ID: <20020823013447.GA18835@nevyn.them.org> (raw)
In-Reply-To: <3D65751B.98E850BA@redhat.com>

On Thu, Aug 22, 2002 at 04:34:51PM -0700, Michael Snyder wrote:
> Daniel Jacobowitz wrote:
> > 
> > Here's two tests I had lying around from when I developed the gdbserver
> > threads support.  Gdbserver passes them with flying colors (if you use my
> > other patch which lets gdbserver run tests properly).  GDB shows a couple of
> > problems, unpredictably (not always repeatable).
> > 
> > OK to add these?
> 
> Hi Joel, 
> 
> I understand the point of schedlock.exp, but what's the point of
> print-threads.exp?  What is it that you're testing?

No specific feature - just the general ability to handle threads doing
things.  It has a slightly different behavior pattern than the other
threads testscases, and triggered different problems.  Oh, and I
remember - there is no other testcase in the testsuite with
pthread_join in it; no threads ever actually exit.  I found some
problems there while I was implementing the gdbserver threads support.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-08-23  1:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-09  8:47 Daniel Jacobowitz
2002-08-13 15:48 ` Fernando Nasser
2002-08-14  9:06   ` Daniel Jacobowitz
2002-08-22 16:41 ` Michael Snyder
2002-08-22 18:35   ` Daniel Jacobowitz [this message]
2002-08-23 12:02     ` Michael Snyder
2002-08-23 12:11       ` Daniel Jacobowitz
2002-08-23 14:08         ` Daniel Jacobowitz
2002-08-23 15:45         ` Michael Snyder

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=20020823013447.GA18835@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@redhat.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