Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: Michael Elizabeth Chastain <mec@shout.net>,
	gdb-patches@sources.redhat.com
Subject: tls test maintainer, was Re: [rfa/testsuite] gdb.threads/tls.{exp,c} fixes
Date: Tue, 29 Jul 2003 21:19:00 -0000	[thread overview]
Message-ID: <3F26E4F0.2070506@redhat.com> (raw)
In-Reply-To: <16166.58698.342251.249709@localhost.redhat.com>

Elena Zannoni wrote:

>Michael Elizabeth Chastain writes:
> > This patch fixes all the ERRORs that I see with
> > native i686-pc-linux-gnu, red hat 8.0, glibc 2.2.93-5-rh.
> > All the results are now PASS, FAIL, KFAIL, and UNSUPPORTED.
> > 
> > The tls.exp change is a one-liner to initialize a variable
> > in all cases (not just the PASS case).
> > 
> > The tls.c change is the calls to sem_wait.  The current code
> > calls sem_wait and then tests errno.  My code calls sem_wait
> > and tests errno only if sem_wait failed.  This is important,
> > because I have observed a lot of test suite hangs caused by
> > return_value = 0, errno = EINTR (happens about 75% to 90% of
> > the time in my test bed).
> > 
> > Tested on native i686-pc-linux-gnu, red hat 8.0, glibc 2.2.93-5-rh,
> > with a variety of gcc's and binutils.
> > 
>
>thanks, seems to work for me too.
>
>elena
>
BTW, although this test is in the gdb.threads directory, of which I'm
listed as the maintainer of record, I'd like to recognize Elena as the
de facto maintainer of this test. ;-)






  reply	other threads:[~2003-07-29 21:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-29 20:44 Michael Elizabeth Chastain
2003-07-29 21:13 ` Elena Zannoni
2003-07-29 21:19   ` Michael Snyder [this message]
2003-07-29 21:24 tls test maintainer, was " Michael Elizabeth Chastain
2003-07-29 21:36 ` Elena Zannoni

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=3F26E4F0.2070506@redhat.com \
    --to=msnyder@redhat.com \
    --cc=ezannoni@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec@shout.net \
    /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