Home
last modified time | relevance | path

Searched refs:watchpoints (Results 1 – 9 of 9) sorted by relevance

/external/valgrind/main/gdbserver_tests/
Dmcwatchpoints.vgtest3 # We need a non buggy gdb.step as watchpoints are placed after a "step".
5 prog: watchpoints
10 argsB: --quiet -l 60 --nx ./watchpoints
Dmcclean_after_fork.vgtest1 # test cleanup of break and watchpoints after fork
Dmcwatchpoints.stdinB.gdb13 # insert the watchpoints
DMakefile.am108 watchpoints program
/external/qemu/
Dcpu-defs.h184 QTAILQ_HEAD(watchpoints_head, CPUWatchpoint) watchpoints; \
Dexec.c596 QTAILQ_INIT(&env->watchpoints); in cpu_exec_init()
1384 QTAILQ_INSERT_HEAD(&env->watchpoints, wp, entry); in cpu_watchpoint_insert()
1386 QTAILQ_INSERT_TAIL(&env->watchpoints, wp, entry); in cpu_watchpoint_insert()
1402 QTAILQ_FOREACH(wp, &env->watchpoints, entry) { in cpu_watchpoint_remove()
1415 QTAILQ_REMOVE(&env->watchpoints, watchpoint, entry); in cpu_watchpoint_remove_by_ref()
1427 QTAILQ_FOREACH_SAFE(wp, &env->watchpoints, entry, next) { in cpu_watchpoint_remove_all()
1755 QTAILQ_INIT(&env->watchpoints); in cpu_copy()
1760 QTAILQ_FOREACH(wp, &env->watchpoints, entry) { in cpu_copy()
2048 QTAILQ_FOREACH(wp, &env->watchpoints, entry) { in tlb_set_page_exec()
2954 QTAILQ_FOREACH(wp, &env->watchpoints, entry) { in check_watchpoint()
Dcpu-exec.c214 QTAILQ_FOREACH(wp, &env->watchpoints, entry) { in cpu_handle_debug_exception()
/external/valgrind/main/coregrind/m_gdbserver/
DREADME_DEVELOPERS103 How are watchpoints implemented ?
116 occurence, gdb sees the value has changed. But the watchpoints are all
333 * "hardware" watchpoint (read/write/access watchpoints) are implemented
/external/valgrind/main/
DNEWS98 memory watchpoints are supported, etc. To use the GDB server, start