Mail Archives: djgpp/2015/05/24/11:00:56
Am 24.05.2015 16:39, schrieb Eli Zaretskii (eliz AT gnu DOT org):
>> Date: Sun, 24 May 2015 14:48:32 +0200
>> From: "Juan Manuel Guerrero (juan DOT guerrero AT gmx DOT de)"<djgpp AT delorie DOT com>
>>
>>> 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.
>
> Thanks for testing.
>
> Is there a reason to withhold this patch? The issues you describe are
> probably additional problems, unrelated to this one.
>
> But if you'd like me to wait, I will.
If you known that the issues are not related to each other then there is no reason to withhold the patch.
Plaes go ahead an commit the patch.
Regards,
Juan M. Guerrero
- Raw text -