Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Will Deacon" <will.deacon@arm.com>
To: "'karthikeyan.s'" <informkarthik@gmail.com>
Cc: "Matthew Gretton-Dann" <Matthew.Gretton-Dann@arm.com>,
	  <gdb@sourceware.org>
Subject: RE: [HELP]Can GDB for ARM set hard breakpoint when native debugging?
Date: Thu, 10 Jun 2010 15:03:00 -0000	[thread overview]
Message-ID: <004901cb08ae$028121a0$078364e0$@deacon@arm.com> (raw)
In-Reply-To: <AANLkTin1s9fmVT_0Z0p5VZwV4EomzysWypODdxwHVsYW@mail.gmail.com>

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



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

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-01 15:06 karthikeyan.s
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 [this message]
     [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='004901cb08ae$028121a0$078364e0$@deacon@arm.com' \
    --to=will.deacon@arm.com \
    --cc=Matthew.Gretton-Dann@arm.com \
    --cc=gdb@sourceware.org \
    --cc=informkarthik@gmail.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