Lines Matching refs:GDB

196 * New and modified GDB server monitor features:
198   - When a signal is reported in GDB, you can now use the GDB convenience
203     with SIGNAL instead of the signal reported to GDB. Use 'signal 0' to
206   - With GDB >= 7.10, the command 'target remote'
209     file yourself, GDB will discover it itself.  See GDB documentation about
558   valgrind feature release.  The built-in GDB server capabilities are
607   - A new GDB server monitor command "info locks" giving the list of
642 * New and modified GDB server monitor features:
646   - The GDB server monitor command "v.info location <address>"
653     ask the GDB server to stop at the start of program execution, at
659   - A new monitor command "v.set hostvisibility" allows the GDB server
1008 * New and modified GDB server monitor features:
1356   - The leak_check GDB server monitor command now can
1362   - Addition of GDB server monitor command 'block_list' that lists
1365   - Addition of GDB server monitor command 'who_points_at' that lists
1432   values to GDB.
1698 * GDB server: Valgrind now has an embedded GDB server.  That means it
1699   is possible to control a Valgrind run from GDB, doing all the usual
1700   things that GDB can do (single stepping, breakpoints, examining
1703   or memory from within GDB when running Memcheck; arbitrarily large
1704   memory watchpoints are supported, etc.  To use the GDB server, start