From 629500fae69737a6230a564e8fef1f42c3ef1116 Mon Sep 17 00:00:00 2001 From: Keith Seitz Date: Tue, 11 Aug 2015 17:09:36 -0700 Subject: Explicit locations: documentation updates This patch adds documentation for explicit locations to both the User Manual and gdb's online help system. gdb/ChangeLog: * NEWS: Mention explicit locations. * breakpoint.c [LOCATION_HELP_STRING]: New macro. [BREAK_ARGS_HELP]: Use LOCATION_HELP_STRING. (_initialize_breakpoint): Update documentation for "clear", "break", "trace", "strace", "ftrace", and "dprintf". gdb/doc/ChangeLog: * gdb.texinfo (Thread-Specific Breakpoints, Printing Source Lines): Use "location(s)"instead of "linespec(s)". (Specifying a Location): Rewrite. Add subsections describing linespec, address, and explicit locations. Add node/menu for each subsection. (Source and Machine Code, C Preprocessor Macros) (Create and Delete Trace points) (Extensions for Ada Tasks): Use "location(s)" instead of "linespec(s)". (Continuing at a Different Address): Remove "linespec" examples. Add reference to "Specify a Location" (The -break-insert Command): Rewrite. Add anchor. Add reference to appropriate manual section discussing locations. (The -dprintf-insert Command): Refer to -break-insert for specification of 'location'. gdb/testsuite/ChangeLog: * gdb.base/help.exp: Update help_breakpoint_text. --- gdb/NEWS | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'gdb/NEWS') diff --git a/gdb/NEWS b/gdb/NEWS index 3fe603615af..950a8664cdd 100644 --- a/gdb/NEWS +++ b/gdb/NEWS @@ -8,6 +8,10 @@ * The 'record instruction-history' command now indicates speculative execution when using the Intel(R) Processor Trace recording format. +* GDB now allows users to specify explicit locations, bypassing + the linespec parser. This feature is also available to GDB/MI + clients. + * New commands maint set target-non-stop (on|off|auto) -- cgit v1.2.1