Re: [HELP]Can GDB for ARM set hard breakpoint when native debugging?

["karthikeyan.s" <informkarthik@gmail.com>]

Hi Will,
Just in case you are going to re-use most of the code for 2.6.35.
In hw_breakpoint.c, the handlers do not release the locks on wtpt/bkpt
not matched.
Should rather be:
 if (val != (unpredictable & ~0x3)) {
    rcu_read_unlock();
    continue;
}

Otherwise I get a "schedule while atomic" bug.

-Karthik

On Tue, Jun 1, 2010 at 8:48 PM, Matthew Gretton-Dann
<matthew.gretton-dann@arm.com> wrote:
> On Tue, 2010-06-01 at 20:35 +0530, karthikeyan.s wrote:
>> Hi,
>> > I've had a go at implementing a backend for hardware watchpoints and breakpoints in the Kernel:
>> > http://lists.infradead.org/pipermail/linux-arm-kernel/2010-March/01117
>> > 0.html
>> Thanks.
>>
>> >I'm hoping to submit a newer version of this patchset against 2.6.35.
>> >I'll add you on CC when I post it to the list. The main changes will be:
>> Thanks again! Looking forward to it.
>>
>> Going through your patch and will be trying it soon. At first sight,
>> seems the gdb changes aren't there in that link. Can you point me to
>> the gdb changes?
>
> We don't have any gdb patches in a releasable state at this moment in
> time.  When the ptrace interface settles down in the 2.6.35 Linux
> kernel, and the updated kernel patch has been submitted, we will submit
> patches to take advantage of hardware breakpoints to gdb.
>
> Thanks,
>
> Matt
>
> --
> Matthew Gretton-Dann
> Principal Engineer - PDSW Tools
> ARM Ltd
>
>



-- 
---
S. Karthikeyan | +919980814745
---