Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: cagney@gnu.org
Cc: gdb@sources.redhat.com
Subject: Re: GDB 6.2 release schedule?
Date: Fri, 18 Jun 2004 15:43:00 -0000	[thread overview]
Message-ID: <20040618154332.EE98F4B104@berman.michael-chastain.com> (raw)

mec> 1677 is probably easy to fix.  1650 looks significantly deeper.
mec> The problem with 1650 is that gdb HEAD randomly gets internal errors,
mec> but gdb 6.1 does not, on the same test script.
ac> These worry me

I'll be looking at 1650 over the weekend.  I doubt that I can fix it
but I can analyze it some more.

ac> (btw, no one got around to moving selftest.exp to 
ac> testsuite/gdb.gdb/ :-).

Is there a PR for it?

ac> But these don't. Presumably being ISA specific its possible to have 
ac> fixes easily pulled into the branch.

Good point.  Some of them are probably hppa-specific or hpux-specific
and easy to fix.

But some of the problems involve watchpoints, so it might be something
that happens on several arches besides hppa-hpux.  All I really know is
that it happens on hppa-hpux and does not happen on i686-linux.

I have to roll up my sleeves and do a bunch of cvs narrowing, which
is a pain on the hp test drive cluster.

Michael C


             reply	other threads:[~2004-06-18 15:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-18 15:43 Michael Elizabeth Chastain [this message]
2004-06-18 17:02 ` Andrew Cagney
  -- strict thread matches above, loose matches on Subject: below --
2004-06-17 21:03 Michael Elizabeth Chastain
2004-06-18 15:33 ` Andrew Cagney
2004-06-29 14:28 ` Randolph Chung
2004-06-17 20:32 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=20040618154332.EE98F4B104@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