This is the mail archive of the
mailing list for the GDB project.
Re: Remote breakpoint problem
>>>>> Andrew Cagney writes:
>> I am porting gdb to a new target processor were remote debugging is used. I have a problem with breakpoints. When I place a breakpoint on foo followed by a continue I see the following communication between gdb and the stub on the other side:
>> - the instruction at foo is saved
>> - foo is replaced by a breakpoint instruction
>> - gdb sends a continue command
>> - the stub reports the breakpoint hit (signal = 5, pc = foo)
>> - gdb replaces the code at foo with the saved instruction
>> - gdb sends a step instruction command
>> - tbe stub reports again a breakpoint hit at foo (signal = 5, pc = foo)
> Shouldn't this stop beyond foo?
I wonder if the stub is flushing the icache after gdb puts the
saved instruction back...