dmbcs/guile
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Clarify --debug' vs. --no-debug'.

Browse source 
* module/ice-9/command-line.scm (*usage*): Attempt to suggest that
  `--no-debug' doesn't inhibit debugging support.

* doc/ref/guile-invoke.texi (Command-line Options): Make it clear that
  `--no-debug' doesn't inhibit debugging support.  Reported by Manuel
  Serrano.
This commit is contained in:
Ludovic Courtès 2011-09-09 00:02:17 +02:00
commit c8286111e0
2 changed files with 8 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

6
doc/ref/guile-invoke.texi
View file

@ -156,6 +156,12 @@ interactive session. When executing a script with @option{-s} or
Do not use the debugging VM engine, even when entering an interactive
session.
Note that, despite the name, Guile running with @option{--no-debug}
@emph{does} support the usual debugging facilities, such as printing a
detailed backtrace upon error. The only difference with
@option{--debug} is lack of support for VM hooks and the facilities that
build upon it (see above).
@item -q
@cindex init file, not loading
@cindex @file{.guile} file, not loading