From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14922 invoked by alias); 4 Nov 2005 09:47:26 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 14878 invoked by uid 22791); 4 Nov 2005 09:47:22 -0000 Received: from ausmtp02.au.ibm.com (HELO ausmtp02.au.ibm.com) (202.81.18.187) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Fri, 04 Nov 2005 09:47:22 +0000 Received: from sd0208e0.au.ibm.com (d23rh904.au.ibm.com [202.81.18.202]) by ausmtp02.au.ibm.com (8.12.10/8.12.10) with ESMTP id jA49fRGW164566 for ; Fri, 4 Nov 2005 20:41:27 +1100 Received: from d23av02.au.ibm.com (d23av02.au.ibm.com [9.190.250.243]) by sd0208e0.au.ibm.com (8.12.10/NCO/VERS6.7) with ESMTP id jA49oGbK183896 for ; Fri, 4 Nov 2005 20:50:19 +1100 Received: from d23av02.au.ibm.com (loopback [127.0.0.1]) by d23av02.au.ibm.com (8.12.11/8.13.3) with ESMTP id jA49lE8R015280 for ; Fri, 4 Nov 2005 20:47:15 +1100 Received: from [9.181.133.252] ([9.181.133.252]) by d23av02.au.ibm.com (8.12.11/8.12.11) with ESMTP id jA49lC77015218; Fri, 4 Nov 2005 20:47:13 +1100 Date: Fri, 04 Nov 2005 11:56:00 -0000 From: Wu Zhou To: ramana.radhakrishnan@codito.com, Joel Brobecker cc: gdb-patches@sources.redhat.com Subject: Re: Suggest closing some old pending PRs In-Reply-To: Message-ID: References: <20051102230031.GJ974@adacore.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2005-11/txt/msg00066.txt.bz2 On Fri, 4 Nov 2005, Wu Zhou wrote: > > > Add to the list, PR 1975 ? > > > > PR1961 can be closed since it no longer crashes gdb . > > > > > > My vote is to close them . > > Yes. I can close that. It is fixed by one of my patch a few monthes ago. I had just closed it. > > > > > Are we looking at targeting any set of PRs for the release ? > > This reminds me that I have some patches and testcases for reviewing. > Most of them is about Fortran (77 and 95) debugging support. Could > I have the pleasure that it get reviewed and into the 6.4 release if > acceptable. Maybe I could glean a list for you maintainers to check? > I will do it today before leaving for home. I had a look at all these fortran related PRs. Some are very old reports, some are already fixed by some patches. and yet soome there is no response. I made some changes to these reports. Some closed if I am sure. Others are waiting for feedback. I update their status here and at the same time ask for advice on how to proceed on some of them. - PR 1880: display of part of an array one of my patch could fix this partially, it can display one-dimension array section (a.k.a sub-array). It is somewhat more difficult to handle multi-dimension. - PR 1768: Seg fault with large programs? There is no testcase, no reproducible steps. And I ask for more context around 5 monthes ago. Didn't get any reply right now. Maybe I can clost this? - PR 1536: gdb 6.0 works with programs compiled with g77 but not HP's f77 HP-UX 11.0 The submitter didn't response for nearly five monthes. And as far as I know we didn't test gdb against HP's f77 compiler code. Maybe we can close this too? - PR 1531/1530: segmentation fault for FOTRAN77 arrays I fixed it a few monthes ago. The submitter said ok to close it. Closed a few monthes ago. - PR 1074: Patches to improve Fortran support This patch is from David Lecomber. And it was already included in another more comprehensive one. As per David's confirmation, I had just closed it. - PR 648: Indexing is incorrect for printing elements of multi-dimensional FORTRAN (g77) array This is already fixed by David Lecomber patch (at least for DWARF reader). And I had coded a testcase for that. Could it get into mainline and gdb-6.4 branch? - PR 822: Finding 'main' in languages other than C/C++ This PR is opened by Elena. And I coded an intial patch to let gdb set fortran main function to "MAIN__", which is used by both g77 and gfortran. Although it could not resolve the error completely. It can let gdb recoginize that the language is fortran after just loading the binary. Could I get this into the source tree and go on to implement the case insensitive symbol lookup for Fortran? - PR 185: gdb can't see f77 source The root cause of this report is the same as PR-822. So I close this as duplicate to that. - PR 939: GDB does not recognise debug information for fortran string correctly. It seems that GDB didn't handle DW_TAG_string_type for Fortran code. The reason might be that both g77 and gfortran handle the string as array of character. That is different than ifc. To support ifc, there might be some more work needed in gdb. - PR 1474: incomplete type Closed by Michael Chastain a years ago. - PR 3: gdb segfaults associated with FORTRAN (g77) array arguments This is closed as per submitter's comments. OK. That is all. Now we have 6 un-closed PRs in fortran aspect. Maybe we can also close a few of them. Could we say that gdb's support of Fortran language is somewhat better than before, maybe in the NEW file? I know that you are discussing that what can and what can't get into that. I am not sure. So I am asking. :-) I am also thinking of enhance gdb's support for new language features introduced after Fortran 77, such as derived type, modular handling and so on. Any suggestion on how to do that is more efficiently and more prone to be accepted into the mainline or 6.4 release? Your advice is highly appreciated. Thanks! Regards - Wu Zhou