From: Florent DEFAY <spira.inhabitant@gmail.com>
To: vladimir@codesourcery.com, gdb@sourceware.org
Subject: Re: Problem with "watch" on a new port.
Date: Thu, 02 Jul 2009 15:11:00 -0000 [thread overview]
Message-ID: <8502af3c0907020810k766a9873qc32552180d5fdc64@mail.gmail.com> (raw)
Thank you.
>This suggest you did not define, or improperly defined, the
>to_stopped_by_watchpoint or to_stopped_data_address or
>to_watchpoint_address_withing_range target methods.
I take inspiration from or1k and I do not find these target methods implemented.
I found them nowhere but in i386 arch, in i386-nat.c.
I do not understand the link between i386-nat.c and the t-dep file.
For my arch, I implemented a t-dep only. How to add a nat? Is it
really necessary?
>> and assignment of results_16[0] not detected.
>
>Is this variable actually modified *before* the execution leaves
>the current scope?
Yes it is.
Regards.
Florent
next reply other threads:[~2009-07-02 15:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 15:11 Florent DEFAY [this message]
2009-07-02 15:42 ` Vladimir Prus
2009-07-02 15:55 ` Jeremy Bennett
2009-07-07 12:29 ` Florent Defay
2009-07-07 15:19 ` Jeremy Bennett
-- strict thread matches above, loose matches on Subject: below --
2009-07-01 9:10 Florent DEFAY
2009-07-01 9:51 ` Vladimir Prus
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=8502af3c0907020810k766a9873qc32552180d5fdc64@mail.gmail.com \
--to=spira.inhabitant@gmail.com \
--cc=gdb@sourceware.org \
--cc=vladimir@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