X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Recipient: djgpp AT delorie DOT com Message-ID: <5561C8A0.2010401@gmx.de> Date: Sun, 24 May 2015 14:48:32 +0200 From: "Juan Manuel Guerrero (juan DOT guerrero AT gmx DOT de)" User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.2.13) Gecko/20101206 SUSE/3.1.7 Thunderbird/3.1.7 MIME-Version: 1.0 To: djgpp AT delorie DOT com Subject: Re: New GDB versions and DJGPP (Was: ANNOUNCE: DJGPP 2.05 beta 1) References: <201505042003 DOT t44K3odg011007 AT delorie DOT com> <555829A6 DOT 8010502 AT iki DOT fi> <555870E8 DOT 7040302 AT iki DOT fi> <201505180114 DOT t4I1EiaX017288 AT envy DOT delorie DOT com> <201505181216 DOT t4ICGaKO014123 AT envy DOT delorie DOT com> <83zj52dkns DOT fsf AT gnu DOT org> <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> <555D5E30 DOT 7020107 AT iki DOT fi> <83vbfl6hs9 DOT fsf AT gnu DOT org> <55618917.7@[87.69.4.28]> <83d21q1g6n DOT fsf AT gnu DOT org> In-Reply-To: <83d21q1g6n.fsf@gnu.org> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:GGOz4mFoNq5UeF3L7zBczx1pDOR7mqt4enrvqpoygY/9t2PcRdI MbkESNAnahIb6FbIvBpaMNOZHopMGjBqnTgSbnqPprzN7IQakDIXqi+qlEqhMYelsHf8/79 /+j8dpwm5f2i3QkvQPVoDW2B4hvwVrKdg1JdNh6gAv5HPJ3TAUSMuck5Eg7vmoPb75w+S1s AtlREPtrU1GQbsNXoZqlw== X-UI-Out-Filterresults: notjunk:1; Reply-To: djgpp AT delorie DOT com Am 24.05.2015 11:24, schrieb Eli Zaretskii (eliz AT gnu DOT org): >> Date: Sun, 24 May 2015 11:17:27 +0300 >> From: "Andris Pavenis (andris DOT pavenis AT iki DOT fi)" >> >>> So what and how goes wrong in the DJGPP build of GDB? Can someone >>> with enough free time step through the go32 initialization, and see >>> what's wrong there? >> >> Perhaps at least some hint could give GDB commit which caused that DJGPP port stopped to work (with >> symptoms described earlier) >> >> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=9b409511d07fe375284701af34909fb539029caf > > Thanks! > > Actually, it seems bd265cd0bde9e045ab5946532449430b66fe91ad, which is > a followup to the one you mentioned, is the bad commit. It seems a > simple case of misunderstanding the API conventions of our read_child > and write_child. > > Can you try the patch below? If it fixes the problem, I will push it. > > diff --git a/gdb/go32-nat.c b/gdb/go32-nat.c > index f3966cd..852473b 100644 > --- a/gdb/go32-nat.c > +++ b/gdb/go32-nat.c > @@ -587,6 +587,13 @@ > else > res = read_child (memaddr, readbuf, len); > > + /* read_child and write_child return zero on success, non-zero on > + failure; adjust the result value to that. */ > + if (res == 0) > + res = len; > + else > + res = -1; > + > if (res<= 0) > return TARGET_XFER_E_IO; > I have tried the patch with gdb 7.9.1 and djgpp support seems to work again. Neitherless sometimes backtrace and finish behave strange. Please give me some time more to check. Especially with djgpp 2.05. Regards, Juan M. Guerrero