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

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

Thanks. Unfortunately, we are not working on 2.6.35. Shortly (I don't
know how soon) we will. I can try this patch only then. I did go
through the patch though.

Regarding the issue I had earlier, it is a NULL pointer dereference at
__sigqueue_alloc
at.
user = get_uid(__task_cred(t)->user);

Seems to be related to the perf event patch I took from arm linux for
your patch.


On Thu, Jun 10, 2010 at 8:32 PM, Will Deacon <will.deacon@arm.com> wrote:
> H Karthik,
>
>> Did you have issue any issues(kernel crash) with the watch_thread_num
>> test gdb test (testsuite) with your gdb changes (And offcourse with
>> you kernel backend!)? ( watch_thread_num is in
>> gdb/testsuite/gdb.base). The issue is not just with watchpoints but
>> also breakpoints. I am using a 2.6.33 kernel for which you had posted
>> the patch version2.
>
> Since you're trying to use this stuff, I've just submitted a new version
> of the patchset:
>
> http://lists.infradead.org/pipermail/linux-arm-kernel/2010-June/017680.html
>
> Please see if the issue occurs with the new code. Unfortunately, I've not
> had a chance to test it because the ptrace interface has changed and I
> don't have a GDB that can `talk the talk'.
>
> Thanks,
>
> Will
>
>
>



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