From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23536 invoked by alias); 26 May 2004 17:15:29 -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 23515 invoked from network); 26 May 2004 17:15:28 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 26 May 2004 17:15:28 -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 i4QHFRi7005215 for ; Wed, 26 May 2004 13:15:27 -0400 Received: from localhost.redhat.com (dhcp64-184.boston.redhat.com [172.16.64.184]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i4QHFR031807; Wed, 26 May 2004 13:15:27 -0400 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 802E62B9D; Wed, 26 May 2004 13:15:21 -0400 (EDT) Message-ID: <40B4D0A9.7080104@gnu.org> Date: Wed, 26 May 2004 17:15: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: Randolph Chung Cc: Joel Brobecker , gdb@sources.redhat.com Subject: Re: GDB 6.1.1 2004-05-21-gmt References: <40B3B907.2030401@gnu.org> <20040525214720.GK10684@gnat.com> <20040525215332.GM7207@tausq.org> <40B3C714.6030605@gnu.org> <20040525222803.GQ7207@tausq.org> In-Reply-To: <20040525222803.GQ7207@tausq.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-05/txt/msg00178.txt.bz2 >>There seem to be a significant number of fixes even without this - >>> basics such as value return and backtraces. >>> >>> As for the arch and other core changes, they can wait until 6.2. > > > ok... it's just that the gdbarch change will fix MANY problems in the > testsuite. :) > > what is the process for getting patches into 6.1? Are they resubmitted > one-by-one, or do i do a wholesale diff of hppa-specific files? There > are about 30 patches from me that has gone into CVS since 6.1. Something like: $ cp src/gdb/hppa*.[hc] 61/src/gdb ; emacs 61/src/gdb/ChangeLog For the changelog suggest both mentioning that the stuff is an import from the mainline and list a concat of the original changelogs (minus dates et.al.). Most important though is: $ emacs 61/src/gdb/NEWS 61/src/gdb/ChangeLog where there should be a brief of how the update affects (benefits) the user - mention a few key bug fixes for instance. When it comes to architecture specific changes GDB is very liberal - the worst they can do is break that architecture and presumably the person pulling in the changes is testing it :-) enjoy, Andrew PS: I've some incompatible frame changes on hold waiting for 6.1.1 to ship - help make these imports easier.