From: Doug Evans <dje@google.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb@sourceware.org, karl leplat <karl.leplat@parrot.com>
Subject: Re: How to use gdbserver for X86 host with arm-linux target ?
Date: Tue, 13 Sep 2011 17:28:00 -0000 [thread overview]
Message-ID: <CADPb22T2-mJ5T7H6JNU7JE9J0KpzZAgCuun73zi_WXqrwMg33w@mail.gmail.com> (raw)
In-Reply-To: <201109121448.18875.pedro@codesourcery.com>
On Mon, Sep 12, 2011 at 6:48 AM, Pedro Alves <pedro@codesourcery.com> wrote:
> On Monday 12 September 2011 12:24:01, karl leplat wrote:
>> Hi,
>>
>> When i inserted a hardware breakpoint, i got the result :
>>
>> Side gdb:
>> Warning:
>> Cannot insert hardware breakpoint 1.
>> Could not insert hardware breakpoints:
>> You may have requested too many hardware breakpoints/watchpoints.
>>
>> Side gdbserver:
>> In the file: "gdbserver/linux-arm-low.c" , i have seen that the target
>> has not registered the function insert_point.
>>
>> Is it normal ?
>
> Yes. The arm-linux gdbserver port was never taught about
> managing breakpoints itself. When that callback is not installed,
> gdb itself inserts breakpoints in program memory, using regular
> memory writes to plant the breakpoint insn.
>
>> Is there a solution ?
>
> There's code in native arm port of gdb to support hardware breakpoints
> and watchpoints (arm-linux-nat.c). Someone interested should be able
> to port it to gdbserver.
Seems like this another example where gdb suffers from having two code
bases (gdb, gdbserver) to implement the same functionality.
[always on the lookout for such things ...]
next prev parent reply other threads:[~2011-09-13 17:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 11:25 karl leplat
2011-09-12 13:48 ` Pedro Alves
2011-09-12 17:24 ` Ulrich Weigand
2011-09-13 17:28 ` Doug Evans [this message]
2011-09-14 12:27 ` Ulrich Weigand
2011-09-14 19:36 ` Stan Shebs
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=CADPb22T2-mJ5T7H6JNU7JE9J0KpzZAgCuun73zi_WXqrwMg33w@mail.gmail.com \
--to=dje@google.com \
--cc=gdb@sourceware.org \
--cc=karl.leplat@parrot.com \
--cc=pedro@codesourcery.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