* gdb.texinfo (Create and Delete Tracepoints): Mention pending
	tracepoint.
---
 gdb/doc/gdb.texinfo |    9 ++++++++-
 1 files changed, 8 insertions(+), 1 deletions(-)

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 0cadc96..7cbf037 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -10337,7 +10337,14 @@ in tracing}).
 If remote stub doesn't support the @samp{InstallInTrace} feature, all
 these changes don't take effect until the next @code{tstart}
 command, and once a trace experiment is running, further changes will
-not have any effect until the next trace experiment starts.
+not have any effect until the next trace experiment starts.  In addition,
+@value{GDBN} supports @dfn{pending tracepoints}---tracepoints whose
+address is not yet resolved.  (This is similar to pending breakpoints.)
+Pending tracepoints are not downloaded to the target and not installed
+until they are resolved.  The resolution of pending tracepoints requires
+@value{GDBN} support--in the remote target, when @value{GDBN}
+disconnects from the remote stub, pending tracepoints still exist but
+can not be resolved while @value{GDBN} is disconnected.
 
 Here are some examples of using the @code{trace} command:
 
-- 
1.7.0.4