aboutsummaryrefslogtreecommitdiffstats
path: root/man/trouble.texi
diff options
context:
space:
mode:
authorGerd Moellmann <[email protected]>2000-02-17 09:49:05 +0000
committerGerd Moellmann <[email protected]>2000-02-17 09:49:05 +0000
commit8389e1e25c7c1aa08f6680b171f56c9f0db5b8c8 (patch)
tree280c50f28a702ca173d6fc4c632f94766f8ac267 /man/trouble.texi
parent1073bdc3f72a37a54cbd274c7ff489d7ec977347 (diff)
*** empty log message ***
Diffstat (limited to 'man/trouble.texi')
-rw-r--r--man/trouble.texi9
1 files changed, 6 insertions, 3 deletions
diff --git a/man/trouble.texi b/man/trouble.texi
index d5f39d56c6..0d942ffa70 100644
--- a/man/trouble.texi
+++ b/man/trouble.texi
@@ -700,9 +700,12 @@ are debugging a running process (not with a core dump).
To make Lisp errors stop Emacs and return to GDB, put a breakpoint at
@code{Fsignal}.
-To find out which Lisp functions are running, using GDB, move up the
-stack, and each time you get to a frame for the function
-@code{Ffuncall}, type these GDB commands:
+For a short listing of Lisp functions running, type the GDB
+command @code{xbacktrace}.
+
+If you want to examine Lisp function arguments, move up the stack, and
+each time you get to a frame for the function @code{Ffuncall}, type
+these GDB commands:
@example
p *args