From: Florent DEFAY <spira.inhabitant@gmail.com>
To: gdb@sourceware.org
Subject: Problem with "watch" on a new port.
Date: Wed, 01 Jul 2009 09:10:00 -0000 [thread overview]
Message-ID: <8502af3c0907010210j519bbdcbh17341eb353e8a921@mail.gmail.com> (raw)
Hi,
I am working on a new port for a 16 bit machine.
step, stepi, next, nexti, breakpoints work well.
The problems come with "watch", it does not work :
(gdb) watch i
Hardware watchpoint 2: i
(gdb) c
Continuing.
Program received signal SIGTRAP, Trace/breakpoint trap.
0x00000174 in main () at main.c:67
67 for (i = 0; i < 10; i++)
(gdb) c
Continuing.
Program received signal SIGTRAP, Trace/breakpoint trap.
0x0000019c in main () at main.c:67
67 for (i = 0; i < 10; i++)
(gdb)
or
(gdb) watch results_16[0]
(gdb) c
Continuing.
and assignment of results_16[0] not detected.
I do not know where to begin to solve this problem.
Please, have you any clue?
Regards.
Florent
next reply other threads:[~2009-07-01 9:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 9:10 Florent DEFAY [this message]
2009-07-01 9:51 ` Vladimir Prus
2009-07-02 15:11 Florent DEFAY
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
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=8502af3c0907010210j519bbdcbh17341eb353e8a921@mail.gmail.com \
--to=spira.inhabitant@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