Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com, gdb-patches@sources.redhat.com
Cc: ezannoni@redhat.com
Subject: Re: RFC: Some expect cleanups for the threads tests
Date: Sun, 27 Jul 2003 17:42:00 -0000	[thread overview]
Message-ID: <200307271742.h6RHgDYC009818@duracef.shout.net> (raw)

It works for me.  Nothing got worse, and several things got better.

The print-threads change has no visible effect in my test bed.

The tls.exp change improves some configurations by giving an UNSUPPORTED
earlier (configurations with gcc HEAD).

The tls-shared.exp change gets rid of a bunch of ERROR/WARNING crap
after the UNSUPPORTED happens.

Recommended for self-approval.

(My test bed is red hat linux 8 with the vendor glibc, and a bunch
of different gcc's and binutils).

Michael C
 
===

2003-07-26  Daniel Jacobowitz  <drow@mvista.com>

	* gdb.threads/print-threads.exp (test_all_threads): Loosen KFAIL
	pattern.
	* gdb.threads/tls-shared.exp: Don't use gdb_suppress_entire_file.
	* gdb.threads/tls.exp: Recognize one case of the host library not
	supporting TLS.


             reply	other threads:[~2003-07-27 17:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-27 17:42 Michael Elizabeth Chastain [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-26 17:31 Michael Elizabeth Chastain
2003-07-26 16:04 Daniel Jacobowitz
2003-07-26 22:48 ` Elena Zannoni
2003-07-26 22:49   ` Daniel Jacobowitz
2003-07-26 23:24     ` Elena Zannoni
2003-07-28  1:00       ` Daniel Jacobowitz

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=200307271742.h6RHgDYC009818@duracef.shout.net \
    --to=mec@shout.net \
    --cc=drow@mvista.com \
    --cc=ezannoni@redhat.com \
    --cc=gdb-patches@sources.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