Re: patch to add HAVE_CONTINUABLE_BREAKPOINT to target_ops

["Kris Warkentin" <kewarken@qnx.com>]

The original message pasted below.  You had asked me to submit a separate
patch.

cheers,

Kris

>> > #define HAVE_CONTINUABLE_WATCHPOINT
>
>>
>> Hmm, this poses an interesting problem.  The other i386 targets have
>> this in their nm.h file, since they consider hardware watchpoints as a
>> native-only feature.  However, this isn't necessarily right since we
>> might support hardware breakpoints via the remote protocol.  If you
>> can live with the native-only approach, please move this to your nm.h
>> file.  Otherwise we might need to multi-arch this definition.
>
>
> Okay, file that under TODO along with the solib stuff.  We have hardware
> breakpoints on all our remote targets that support them.

Just FYI, this needs to be added to the target vector (target.h) and not
the architecture vector.

For examples, see STOPPED_BY_WATCHPOINT et.al.  A bit of manipulation of
the existing nm-*.h files will be needed - have them define the value as 1.

Can you please submit a separate patch that does just this.

Andrew

----- Original Message -----
From: "Andrew Cagney" <ac131313@redhat.com>
To: "Kris Warkentin" <kewarken@qnx.com>
Cc: <gdb-patches@sources.redhat.com>
Sent: Wednesday, February 19, 2003 7:46 PM
Subject: Re: patch to add HAVE_CONTINUABLE_BREAKPOINT to target_ops


> Kris,
>
> I remember asking a question about debug info (so that set debug target
> 1) did something useful (or did I misremember?).
>
> Andrew
>
>