From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: cagney@gnu.org, mec.gnu@mindspring.com
Cc: gdb@sources.redhat.com
Subject: Re: gdb 6.2 blockers
Date: Tue, 06 Jul 2004 20:03:00 -0000 [thread overview]
Message-ID: <20040706200342.4EEED4B104@berman.michael-chastain.com> (raw)
ac> BTW, I did try to reproduce this bug. Mainline GDB and manythreads.exp
ac> appear to work everytime on NPTL based FC2 and RHEL2 GNU/Linux systems
ac> (well at least for the 30+ test runs I tried). That wasn't the case
ac> with 6.1.
Cool. Could you cc: gdb-gnats on that? I'm trying to use gnats to
collect history for complicated bugs like this.
I'm adding an RHEL3 machine soon. hp test drive has an eight processor
machine running RHEL3!
ac> We should probably mention this fix in the NEWS file, and the apparent
ac> linuxthreads regression in PROBLEMS.
If the PR is listed in PROBLEMS then it's totally okay with me.
(In my dream world, a user sees the PR number in PROBLEMS, reads the PR
to acquire all the information that we've discovered, and becomes
motivated to fix the problem and join the gdb developer community).
Michael C
next reply other threads:[~2004-07-06 20:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-06 20:03 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-06 20:56 Michael Elizabeth Chastain
2004-07-06 18:24 Michael Elizabeth Chastain
2004-07-06 19:14 ` Andrew Cagney
2004-07-06 19:32 ` Manoj Iyer
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=20040706200342.4EEED4B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=cagney@gnu.org \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).