Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Chastain <mec.gnu@mindspring.com>
To: cagney@gnu.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc/6.2] Mention threads in NEWS and PROBLEMS
Date: Wed, 28 Jul 2004 21:36:00 -0000	[thread overview]
Message-ID: <41081C6A.nail5AH1BTNHU@mindspring.com> (raw)
In-Reply-To: <4107B8CC.6090001@gnu.org>

> Separatly, what about HP/UX?  Is that a regression or a long standing bug?

I let hpux get away from me for this release.  :-(

My most recent results are in:

  http://sources.redhat.com/ml/gdb-testers/2004-q3/msg00012.html

There are 14 test scripts with regressions in the results from gdb 6.1.1
to gdb HEAD 2004-07-02.  From experience, about 20% of those will turn
out to be actual gdb bugs, so I expect 2-3 actual gdb bugs.

None of the regressions are in gdb.threads.  In particular,
manythreads.exp is broken with both 6.1.1 and gdb HEAD.
So it's a long-standing bug.

Michael C


  reply	other threads:[~2004-07-28 21:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-28  4:08 Andrew Cagney
2004-07-28  6:06 ` Andrew Cagney
2004-07-28  6:25   ` Michael Chastain
2004-07-28 14:31     ` Andrew Cagney
2004-07-28 21:36       ` Michael Chastain [this message]
2004-07-28 18:02   ` Eli Zaretskii
2004-07-28 19:54   ` Andrew Cagney

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=41081C6A.nail5AH1BTNHU@mindspring.com \
    --to=mec.gnu@mindspring.com \
    --cc=cagney@gnu.org \
    --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