gdb/doc/

	* gdb.texinfo (Starting and Stopping Trace Experiments): Fix
	circular-trace-buffer name.

diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index c77ff269993a344f1966ff9c3c7850dba3ec4f09..d5d29a7b38340817b01858e42b45adcd0b673f8d 100644 (file)
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -2,6 +2,9 @@
 
        * gdb.texinfo (Tracepoint Conditions): Fix missing parenthesis.
 
+       * gdb.texinfo (Starting and Stopping Trace Experiments): Fix
+       circular-trace-buffer name.
+
 2011-02-28  Joel Brobecker  <brobecker@adacore.com>
 
        * gdb.texinfo (Inferiors and Programs): Fix small error introduced

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 1b353c486940d9aff6bcc46c9d90296982fcd172..a5eaa729b89fec11c1beda36e6f42bef69da2bae 100644 (file)
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -10469,7 +10469,7 @@ frames, oldest first, until there is enough room to continue
 collecting.  This is especially useful if your tracepoints are being
 hit too often, and your trace gets terminated prematurely because the
 buffer is full.  To ask for a circular trace buffer, simply set
-@samp{circular_trace_buffer} to on.  You can set this at any time,
+@samp{circular-trace-buffer} to on.  You can set this at any time,
 including during tracing; if the agent can do it, it will change
 buffer handling on the fly, otherwise it will not take effect until
 the next run.