Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Matthew Gretton-Dann <matthew.gretton-dann@arm.com>
To: xingxing pan <forandom@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: [HELP]Can GDB for ARM set hard breakpoint when native debugging?
Date: Fri, 28 May 2010 09:28:00 -0000	[thread overview]
Message-ID: <1275038883.23133.51.camel@e102319-lin.cambridge.arm.com> (raw)
In-Reply-To: <AANLkTinHIdHmkoXyou1g_CfkOIvKdOFND_tlvYqdvuzb@mail.gmail.com>

Hi,

On Fri, 2010-05-28 at 14:00 +0800, xingxing pan wrote:
> Hey guys, can GDB for ARM set hard breakpoint when native debugging?
> I found GDB for i386 use the ptrace(POKE_USER,...) to set hard
> breakpoint. But in ARM's code I can't find such similar facility.

GDB does not use hardware breakpoints when debugging native ARM Linux
applications.

> Dose ARM has some hardware unit to support hard breakpoint?

Some ARM CPUs have hardware breakpoint support (for instance all current
Cortex-A processors).  However, the number of hardware breakpoints
available varies depending on the CPU.

Thanks,

Matt

-- 
Matthew Gretton-Dann
Principal Engineer - PDSW Tools
ARM Ltd


  parent reply	other threads:[~2010-05-28  9:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-28  6:00 xingxing pan
2010-05-28  6:22 ` xingxing pan
2010-05-28  9:28 ` Matthew Gretton-Dann [this message]
     [not found]   ` <113ACA888B71994BB56E5CF3704953486BAA6A18D8@BGMAIL02.nvidia.com>
2010-06-01  9:06     ` Will Deacon
2010-05-28 11:20 ` Simon Richter
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
     [not found]         ` <-2775908164685299161@unknownmsgid>
2010-06-13 13:00           ` karthikeyan.s

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=1275038883.23133.51.camel@e102319-lin.cambridge.arm.com \
    --to=matthew.gretton-dann@arm.com \
    --cc=forandom@gmail.com \
    --cc=gdb@sourceware.org \
    /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