From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16575 invoked by alias); 18 Jun 2004 17:02:14 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 16559 invoked from network); 18 Jun 2004 17:02:12 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 18 Jun 2004 17:02:12 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i5IH2Ce3003581 for ; Fri, 18 Jun 2004 13:02:12 -0400 Received: from localhost.redhat.com (porkchop.devel.redhat.com [172.16.58.2]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i5IH2B009814; Fri, 18 Jun 2004 13:02:12 -0400 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 6C8FF2B9D; Fri, 18 Jun 2004 13:01:59 -0400 (EDT) Message-ID: <40D32007.4050009@gnu.org> Date: Fri, 18 Jun 2004 17:02:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040217 MIME-Version: 1.0 To: Michael Elizabeth Chastain Cc: gdb@sources.redhat.com Subject: Re: GDB 6.2 release schedule? References: <20040618154332.EE98F4B104@berman.michael-chastain.com> In-Reply-To: <20040618154332.EE98F4B104@berman.michael-chastain.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-06/txt/msg00198.txt.bz2 > 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? It's just a todo item, after gdb.gdb/ was created, no one got around to moving selftest.exp there (the test gdb debugging gdb directory), oops :-) > 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. FYI,JeffJ's already narrowed the watchpoint regressions down to a specific patch, so I think that's under control. > I have to roll up my sleeves and do a bunch of cvs narrowing, which > is a pain on the hp test drive cluster. Andrew