X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient:	djgpp AT delorie DOT com
Message-ID:	<555D5E30.7020107@iki.fi>
Date:	Thu, 21 May 2015 07:25:20 +0300
From:	"Andris Pavenis (andris DOT pavenis AT iki DOT fi)" <djgpp AT delorie DOT com>
User-Agent:	Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version:	1.0
To:	djgpp AT delorie DOT com
Subject:	Re: ANNOUNCE: DJGPP 2.05 beta 1
References:	<201505042003 DOT t44K3odg011007 AT delorie DOT com> <55579278 DOT 8090301 AT iki DOT fi> <CAA2C=vBaQKzmch_buxFm20DJLcG+zv6d6803+qMEx=baA4Frog AT mail DOT gmail DOT com> <555829A6 DOT 8010502 AT iki DOT fi> <CAA2C=vA73qPvoDFytp3FeW6bCD1-XuGsFFoDinoKn2KYY1fkow AT mail DOT gmail DOT com> <555870E8 DOT 7040302 AT iki DOT fi> <CAA2C=vDhD6BJj89o1i0FRd2U0H4bTpGGN4zH6qs7FJKxzqhuQg AT mail DOT gmail DOT com> <201505180114 DOT t4I1EiaX017288 AT envy DOT delorie DOT com> <CAA2C=vCyrQ_+Yq6XsRD-UO4r=j9WoGGiXoqQFrkbiEQpzX+=MA AT mail DOT gmail DOT com> <201505181216 DOT t4ICGaKO014123 AT envy DOT delorie DOT com> <CAA2C=vCk5MY74z+HNVzzdLByg71Y_9ObK-1jPxJ_KF8eqRDZMQ AT mail DOT gmail DOT com> <83zj52dkns DOT fsf AT gnu DOT org> <CAA2C=vAPcN+MKC_2tcZqVmo9gvF2Cxdo+K+-qfKaNrQuCkMnEw AT mail DOT gmail DOT com> <555A0DD5 DOT 1010607 AT iki DOT fi> <83r3qdemuj DOT fsf AT gnu DOT org> <555AADE6 DOT 3030905 AT iki DOT f> <83lhgkehn4 DOT fsf AT gnu DOT org> <201505191714 DOT t4JHEr0B010992 AT envy DOT delorie DOT com> <83vbfo7a74 DOT fsf AT gnu DOT org> <201505191729 DOT t4JHTIRe011541 AT envy DOT delorie DOT com> <83sias77km DOT fsf AT gnu DOT org> <555CFF9C DOT 1050301 AT gmx DOT de>
In-Reply-To:	<555CFF9C.1050301@gmx.de>
Reply-To:	djgpp AT delorie DOT com

On 05/21/2015 12:41 AM, Juan Manuel Guerrero (juan DOT guerrero AT gmx DOT de) wrote:
>
> Today I have ported and compiled gdb-7.9.1.tar.gz.  The COFF/dwarf support is
> as broken as with gdb-7.8. and later versions.  The last gdb version with working
> djgpp support is gdb-7.7.1.tar.gz.  I do not think that they have intentionally
> removed or brocken djgpp support.  But an inspection of the changelog file shows
> that they have modified go32-nat.c but not only this one.  This change seems to be
> part of a major modification or rewrite of that particular code segments.
>
> From Changelog-2014:
>
> 2014-03-07  Pedro Alves  <palves AT redhat DOT com>
>
>     * go32-nat.c: Include inf-child.h.
>     (go32_ops): Delete global.
>     (go32_close, go32_detach, go32_prepare_to_store, go32_can_run):
>     Delete methods.
>     (go32_create_inferior): Push the passed in target pointer instead
>     of referencing go32_ops.
>     (init_go32_ops): Delete function.  Moved parts to _initialize_go32_nat.
>     (go32_target): New function, based on init_go32_ops, but inherit
>     inf_child_target.
>     (_initialize_go32_nat): Use go32_target.  Move parts of
>     init_go32_ops here.
>
> I have inspected those changes and they seem to have been well done.  So it is
> not clear what has been brocken.
> Unfortunately I have absolute no knowledge about DWARF and especially I do not
> understand how the djgpp support of gdb works.  So I cannot debug nor figure out
> this issue.

This change is most likely only a result of other changes. So if we do not know these other changes 
it would be very difficult to see whether that go32-nat.c change is actually OK or some detail is 
accidentally left out.

Perhaps it is necessary to look for in GDB GIT repository to see which change actually broke DJGPP 
support between creating gdb_7_7_branch and gdb-7.8 release. 'git bisect' could perhaps help. Then 
it could be more clear what went wrong

Andris

- Raw text -