public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdb 6.2 blockers
Date: Tue, 06 Jul 2004 19:14:00 -0000	[thread overview]
Message-ID: <40EAFA1C.7020108@gnu.org> (raw)
In-Reply-To: <20040706182423.393F34B104@berman.michael-chastain.com>

> ac> - 1650 is an issue, but even there I'm wondering how much.  It's ticking 
> ac> a horrible nasty race condition and may not be a real problem in the 
> ac> field - do people really run 100 thread programs using linuxthreads.
> 
> 1650, manythreads.exp, works every time with gdb 6.1.1.
> So if there's a kernel race condition then gdb does not trigger it
> and gdb HEAD does.  This is a user-visible regression.

BTW, I did try to reproduce this bug.  Mainline GDB and manythreads.exp 
appear to work everytime on NPTL based FC2 and RHEL2 GNU/Linux systems 
(well at least for the 30+ test runs I tried).  That wasn't the case 
with 6.1.

We should probably mention this fix in the NEWS file, and the apparent 
linuxthreads regression in PROBLEMS.

Andrew


  reply	other threads:[~2004-07-06 19:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-06 18:24 Michael Elizabeth Chastain
2004-07-06 19:14 ` Andrew Cagney [this message]
2004-07-06 19:32 ` Manoj Iyer
  -- strict thread matches above, loose matches on Subject: below --
2004-07-06 20:56 Michael Elizabeth Chastain
2004-07-06 20:03 Michael Elizabeth Chastain
2004-07-06 17:07 Andrew Cagney
2004-07-07 15:26 ` Andrew Cagney
2004-07-07 16:12   ` 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=40EAFA1C.7020108@gnu.org \
    --to=cagney@gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=mec.gnu@mindspring.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).