Re: Incorrect behavior in case of watchpoint

On Fri, Sep 1, 2017 at 6:32 PM, Aetf <[email protected]> wrote:
> Hi,
>
> I'm afraid I don't have much time for this at the moment. Actually this has
> been on my todo list for a while... I'll take a look at it soon.
>
> Cheers,
> Aetf
>
> On Fri, Sep 1, 2017 at 7:55 AM Aleix Pol <[email protected]> wrote:
>>
>> On Mon, Aug 21, 2017 at 1:54 PM, Aleksey Midenkov <[email protected]>
>> wrote:
>> > I've set watchpoint with command `watch -l` and it was saved in
>> > KDevelop session. Now it doesn't start debug session because it ends
>> > up in endless loop:
>> >
>> > (gdb) 2106-break-watch "-location m_part_spec.start_part"
>> > 2106^error,msg="-break-watch: Unknown option ``location
>> > m_part_spec.start_part''"
>> > (gdb) 2107-break-watch "-location m_part_spec.start_part"
>> > 2107^error,msg="-break-watch: Unknown option ``location
>> > m_part_spec.start_part''"
>> > (gdb) 2108-break-watch "-location m_part_spec.start_part"
>> > 2108^error,msg="-break-watch: Unknown option ``location
>> > m_part_spec.start_part''"
>> > (gdb) 2109-break-watch "-location m_part_spec.start_part"
>> > 2109^error,msg="-break-watch: Unknown option ``location
>> > m_part_spec.start_part''"
>> > (gdb) 2110-break-watch "-location m_part_spec.start_part"
>> > 2110^error,msg="-break-watch: Unknown option ``location
>> > m_part_spec.start_part''"
>> > ...
>> >
>> > Though I've managed to delete breakpoint from Breakpoints tab and start
>> > again.
>>
>> Hey Aetf,
>> Any idea why that could be?
>>
>> Aleix
>>
>> PS: Aleksey, can you make sure this is reported in bugs.kde.org?

Hi Aetf,
Maybe you can give us some pointers in case someone else can/wants to fix it?

Aleix