HomeSort by relevance Sort by last modified time
    Searched full:watchpoint (Results 1 - 25 of 51) sorted by null

1 2 3

  /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/chromium_org/v8/test/webkit/
dfg-patchable-get-by-id-after-watchpoint.js 25 "This tests that a patchable GetById right after a watchpoint has the appropriate nop padding."
30 var b = o.f; // Watchpoint.
62 // Cause first the watchpoint on o.f to fire, and then the GetById
64 O.prototype.g = 57; // Fire the watchpoint.
dfg-proto-stub-watchpoint-fire.js 25 "Tests that we don't crash if a watchpoint on prototype access stubs is fired."
  /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/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/coregrind/m_gdbserver/
target.h 132 gdb about the encountered watchpoint.
137 /* Returns 1 if target was stopped due to a watchpoint hit, 0 otherwise. */
140 /* Returns the address associated with the watchpoint that hit, if any;
190 /* Insert and remove a hardware watchpoint.
193 2 = write watchpoint
194 3 = read watchpoint
195 4 = access watchpoint
m_gdbserver.c 70 watch_reason, // watchpoint detected by tool
325 void VG_(needs_watchpoint) (Bool (*watchpoint) (PointKind kind,
330 tool_watchpoint = watchpoint;
369 g = VG_(arena_malloc)(VG_AR_CORE, "gdbserver_point watchpoint",
424 /* If no overlap, examine next watchpoint: */
430 matches the watchpoint kind. */
434 /* Watchpoint encountered.
435 If this is a read watchpoint, we directly call gdbserver
437 Otherwise, for a write watchpoint, we have to finish
441 For a read watchpoint, we better call gdbserver directly
    [all...]
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
target.c 180 2 => single stepping asked by valgrind (watchpoint) */
229 dlog(1, "clearing watchpoint stopped_data_address %p\n",
  /development/tutorials/ReverseDebug/
README.txt 112 Hardware watchpoint 2: *(&p)
115 Hardware watchpoint 2: *(&p)
  /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/valgrind/main/none/tests/
cmdline1.stdout.exp 20 full is slower but provides precise watchpoint/step
  /external/qemu/target-mips/
helper.c 558 [EXCP_DFWATCH] = "deferred watchpoint",
560 [EXCP_IWATCH] = "instruction fetch watchpoint",
574 [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...]

Completed in 1262 milliseconds

1 2 3