| /external/valgrind/main/gdbserver_tests/ |
| mcwatchpoints.stdoutB.exp | 5 Hardware read watchpoint 2: undefined[0]
6 Hardware access (read/write) watchpoint 3: undefined[4]
7 Hardware watchpoint 4: undefined[8]
9 Hardware read watchpoint 2: undefined[0]
14 Hardware access (read/write) watchpoint 3: undefined[4]
19 Hardware access (read/write) watchpoint 3: undefined[4]
25 Hardware watchpoint 4: undefined[8]
|
| mcclean_after_fork.stdinB.gdb | 15 # put a read watchpoint on mem
16 # we expect that the read watchpoint is not triggered in the child
22 # we should now have encountered the read watchpoint in the parent.
|
| mcclean_after_fork.stdoutB.exp | 7 Hardware read watchpoint 4: mem
9 Hardware read watchpoint 4: mem
|
| mcwatchpoints.vgtest | 1 # test the memcheck watchpoint functionality
2 # Note: we need --vgdb=full to stop at the instruction following the watchpoint.
|
| watchpoints.c | 15 read watchpoint at 0,
|
| /external/qemu/ |
| gdbstub.h | 6 /* GDB breakpoint/watchpoint types */
|
| exec.c | [all...] |
| cpu-all.h | 844 /* Breakpoint/watchpoint flags */
859 int flags, CPUWatchpoint **watchpoint);
862 void cpu_watchpoint_remove_by_ref(CPUState *env, CPUWatchpoint *watchpoint);
|
| /external/valgrind/main/coregrind/m_gdbserver/ |
| target.h | 108 /* Insert and remove a hardware watchpoint.
111 2 = write watchpoint
112 3 = read watchpoint
113 4 = access watchpoint
119 /* Returns 1 if target was stopped due to a watchpoint hit, 0 otherwise. */
123 /* Returns the address associated with the watchpoint that hit, if any;
|
| README_DEVELOPERS | 107 supports this : when a watchpoint is placed, memcheck changes
110 is due to a watchpoint and gives the control back to gdb.
111 Stopping on the exact instruction for a write watchpoint implies
114 and so "does not believe" the information that the write watchpoint
115 was triggered, and continues the execution. At the next watchpoint
118 terminate the current instruction before reporting the write watchpoint.
122 See m_gdbserver.c Bool VG_(is_watched) where watchpoint handling
333 * "hardware" watchpoint (read/write/access watchpoints) are implemented
334 but can't persuade gdb to insert a hw watchpoint of what valgrind
348 A small patch in gdb remote.c allowed to control the remote target watchpoint
[all...] |
| m_gdbserver.c | 68 watch_reason, // watchpoint detected by tool
286 void VG_(needs_watchpoint) (Bool (*watchpoint) (PointKind kind,
291 tool_watchpoint = watchpoint;
326 g = VG_(arena_malloc)(VG_AR_CORE, "gdbserver_point watchpoint",
369 /* If no overlap, examine next watchpoint: */
375 matches the watchpoint kind. */
379 /* Watchpoint encountered.
380 If this is a read watchpoint, we directly call gdbserver
382 Otherwise, for a write watchpoint, we have to finish
386 For a read watchpoint, we better call gdbserver directly
[all...] |
| valgrind-low.c | 507 2 => single stepping asked by valgrind (watchpoint) */
522 dlog(1, "clearing watchpoint stopped_data_address %p\n",
|
| server.c | 929 /* No watchpoint support or not a watchpoint command;
955 /* No watchpoint support or not a watchpoint command;
[all...] |
| /external/eclipse-basebuilder/basebuilder-3.6.2/org.eclipse.releng.basebuilder/plugins/org.eclipse.jdt.debug_3.6.1.v20100715_r361/ |
| plugin.properties | 37 JavaWatchpoint.name = Java Watchpoint
|
| /external/valgrind/main/include/ |
| pub_tool_gdbserver.h | 88 accessibility for watchpoint support.
100 /* watchpoint support --------------------------------------*/
104 the access provided by the tool matches the watchpoint kind.
119 // Must return True if the watchpoint has been properly inserted or
127 Bool (*watchpoint) (PointKind kind, Bool insert, Addr addr, SizeT len)
|
| /external/valgrind/main/none/tests/ |
| cmdline1.stdout.exp | 20 full is slower but provides precise watchpoint/step
|
| cmdline2.stdout.exp | 20 full is slower but provides precise watchpoint/step
|
| /prebuilts/gcc/linux-x86/mips/mipsel-linux-android-4.6/bin/ |
| mipsel-linux-android-gdb | |
| mipsel-linux-android-gdbtui | |
| /prebuilts/gcc/linux-x86/x86/i686-linux-android-4.6/bin/ |
| i686-linux-android-gdb | |
| i686-linux-android-gdbtui | |
| /external/kernel-headers/original/asm-mips/ |
| cpu.h | 241 #define MIPS_CPU_WATCH 0x00000100 /* watchpoint registers */
|
| /external/qemu/target-mips/ |
| helper.c | 518 [EXCP_DFWATCH] = "deferred watchpoint",
520 [EXCP_IWATCH] = "instruction fetch watchpoint",
534 [EXCP_DWATCH] = "data watchpoint",
|
| /external/valgrind/main/docs/xml/ |
| manual-core-adv.xml | 694 tool reporting an error or to a watchpoint. If the gdbserver
712 <para>Hardware watchpoint support by the Valgrind
717 only Memcheck provides hardware watchpoint simulation. The
718 hardware watchpoint simulation provided by Memcheck is much
721 instruction. Hardware watchpoint simulation also provides read
722 watchpoints. The hardware watchpoint simulation by Memcheck has
729 4 hardware watchpoints, each watchpoint watching 1, 2, 4 or 8
738 <para>Memcheck implements hardware watchpoint simulation by
740 a hardware watchpoint is removed, the range is marked as
741 addressable and defined. Hardware watchpoint simulation o
[all...] |
| /external/valgrind/main/coregrind/ |
| pub_core_gdbserver.h | 57 Write/read/access watchpoint can only be provided by tools which are
|
