From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: cagney@gnu.org, drow@mvista.com
Cc: gdb@sources.redhat.com, jimb@redhat.com
Subject: Re: GDB 6.2
Date: Wed, 30 Jun 2004 10:06:00 -0000 [thread overview]
Message-ID: <20040629173942.F1F3C4B104@berman.michael-chastain.com> (raw)
drow> 1677 is fixed by Bob's patch (not sure if he's checked it in yet).
drow> I have no reason to think that manythreads.exp is fixed, though.
Daniel's right, as usual.
Also there are some hppa-hpux regressions. I've filed only one PR so
far, gdb/1692. Jeff J updated the code in bpstat_stop_status so I have
to run another spin. It might be fixed. It might not.
That's all the things I know about:
1650 manythreads, waiting for investigation (daniel j)
1677 symtab fullname, waiting for patch commit + retest (michael c)
1692 hpux watchpoint, waiting for retest (michael c)
about 15 more unanalyzed hppa-hpux testsuite regressions (michael c)
Michael C
next reply other threads:[~2004-06-29 17:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 10:06 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-29 15:33 Andrew Cagney
2004-06-29 15:41 ` 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=20040629173942.F1F3C4B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=cagney@gnu.org \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@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