X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
Message-ID: <53E68267.6060306@gmx.de>
Date: Sat, 09 Aug 2014 22:19:51 +0200
From: Juan Manuel Guerrero <juan DOT guerrero AT gmx DOT de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.7.0
MIME-Version: 1.0
To: djgpp AT delorie DOT com
Subject: Re: gdb 7.8 no longer works with DJGPP.
References: <53E51B98 DOT 1080807 AT gmx DOT de> <834mxmn3vi DOT fsf AT gnu DOT org> <53E55CC7 DOT 1000905 AT gmx DOT de> <83y4uykuzv DOT fsf AT gnu DOT org>
In-Reply-To: <83y4uykuzv.fsf@gnu.org>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID:  V03:K0:LHbe9F4nBKZT/SF4qEcq2uvtKpcTh/7ED3jW7V7AOcLujdWHvED
 zVh2pF5xf18uXU9mqhqvOcGy63S5j/SHAa95uvWZ09rMBLh5X6MGWlstiVqglhOHDs7OFlQ
 tG/eqvTYVGHlWs4V4zHyhRyjgVlJF8lduIM7Ag1Zb7Ncx7tQoSTWIuFna4RBdaG0N+HPjpy
 kQ43n0DXVTKrlv3KBH33A==
X-UI-Out-Filterresults: notjunk:1;
Reply-To: djgpp AT delorie DOT com

Am 09.08.2014 09:00, schrieb Eli Zaretskii:

>> (gdb) r
>> Starting program: h:/l/bins/bin/a.exe
>> Warning:
>> Cannot insert breakpoint 1.
>> Cannot access memory at address 0x1e04
> This means inserting a breakpoint at 0x1e04 returned EIO.  I suggest
> to take a good look at the code that's involved in this.  I see that
> in GDB-7.7.1, we had these 2 lines in go32-nat.c:
>
>    go32_ops.to_insert_breakpoint = memory_insert_breakpoint;
>    go32_ops.to_remove_breakpoint = memory_remove_breakpoint;
>
> but these lines are no longer there, and instead the go32 target
> inherits from inf_child_target.  Perhaps that's the cause of the
> problem.

Thank you for the pointer.  The change from the old way to handle the
native support to the new way of initializing struct target_ops inf_child_ops
by inf_child_target and go32_target seems to be the source of the difficulties.
At least go32_ops.to_insert_breakpoint and go32_ops.to_remove_breakpoint are
not set to the corresponding equivalent new variables for DJGPP. This makes
the current version of GDB useless for DJGPP.  There may be even more missing
variables.  It will take same days until I become familiar enough with the old
code and the new code to be able to fix this.  As soon as I have figured out
how to fix this I will propose a patch for GDB.

Regards,
Juan M. Guerrero