Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "karthikeyan.s" <informkarthik@gmail.com>
To: Will Deacon <will.deacon@arm.com>
Cc: gdb@sourceware.org, Matthew Gretton-Dann <matthew.gretton-dann@arm.com>
Subject: RE: [HELP]Can GDB for ARM set hard breakpoint when native debugging?
Date: Tue, 01 Jun 2010 15:06:00 -0000	[thread overview]
Message-ID: <AANLkTilUjMpOvt3U2KbYSPLKMZ-g915qyA_S2-UVt7F1@mail.gmail.com> (raw)

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.

> It's worth noting that using the context-id based watchpoint will
> almost certainly break in the case of ASID rollover for a process. It
> also won't allow you to install watchpoints on a per-thread basis afaict.
Yeah I agree. Not sure about the per-thread hypothesis.

>The HW-breakpoint framework inserts/removes breakpoints on context
>switch so the need for hardware assisted context id matching is removed.
This was my next step. I thought context id based implementation would
let me get familiar with what I am doing quickly and then I can take
up context-switch-time bkpt insertion.
But you beat me to it totally!

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?

Thanks,
Karthik


             reply	other threads:[~2010-06-01 15:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-01 15:06 karthikeyan.s [this message]
2010-06-01 15:18 ` Matthew Gretton-Dann
2010-06-03 11:39   ` karthikeyan.s
2010-06-03 11:54     ` Will Deacon
     [not found]     ` <-3629479195726626766@unknownmsgid>
2010-06-10 14:40       ` karthikeyan.s
2010-06-10 15:03         ` Will Deacon
     [not found]         ` <-2775908164685299161@unknownmsgid>
2010-06-13 13:00           ` karthikeyan.s
  -- strict thread matches above, loose matches on Subject: below --
2010-05-28  6:00 xingxing pan
2010-05-28  6:22 ` xingxing pan
2010-05-28  9:28 ` Matthew Gretton-Dann
     [not found]   ` <113ACA888B71994BB56E5CF3704953486BAA6A18D8@BGMAIL02.nvidia.com>
2010-06-01  9:06     ` Will Deacon
2010-05-28 11:20 ` Simon Richter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTilUjMpOvt3U2KbYSPLKMZ-g915qyA_S2-UVt7F1@mail.gmail.com \
    --to=informkarthik@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=matthew.gretton-dann@arm.com \
    --cc=will.deacon@arm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox