X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Recipient: djgpp AT delorie DOT com Message-ID: <49FD42B3.90003@iki.fi> Date: Sun, 03 May 2009 10:07:31 +0300 From: Andris Pavenis User-Agent: Thunderbird 2.0.0.21 (X11/20090320) MIME-Version: 1.0 To: djgpp AT delorie DOT com Subject: Re: Please help resurrecting GDB for version 7.0 release References: <83zldveryw DOT fsf AT gnu DOT org> In-Reply-To: <83zldveryw.fsf@gnu.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: djgpp AT delorie DOT com Eli Zaretskii kirjoitti: > The last version of GDB ported to DJGPP was 6.1. That was 5 years > ago. GDB 6.1 also has a couple of nasty bugs (for example, the > `finish' command triggers an internal GDB error). > > GDB 7.0 is slated for release in early June this year, and I thought > it would be a good idea to resurrect the DJGPP port in time for that. > With that in mind, I set out to build the current CVS code base, debug > whatever problems I find, and start using it in my occasional DJGPP > related work. > > I'm now past the initial configury and compilation problems, and > working on the problems I find as I go. (People who want details can > track my progress by reading my messages posted to the > gdb-patches AT sourceware DOT org and gdb AT sourceware DOT org mailing lists.) > Most of the problems I had on my initial list are already solved, but > a few are still pending. > In meanwhile one can take look at my build of GDB-6.8. http://ap1.pp.fi/djgpp/gdb/6.8/ It not tested much though. I thought that I had put it at http://ap1.pp.fi about half a year ago when I built it, but it was not so unfortunately. So I'm putting it there now. It is not tested much though and can only be built when DJGPP v2.04 is being used. I also had problems with additional registers not supported for DJGPP and had to patch related source code as far as I remember. Andris PS. Some days ago had to update in CentOS-5 gdb-6.5 to 6.8 due to problems with breakpoints in 6.5. As far as I remember I have had the same breakpoint (and backtrace) problem also for DJGPP earlier.