summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJan Michael Greiner <jan0michael@yahoo.com>2018-06-12 15:10:09 +0200
committerJan Michael Greiner <jan0michael@yahoo.com>2018-06-12 15:10:09 +0200
commitff982623dc1d3c3df0f5c0de3f270c1c62a1820e (patch)
tree1b05d55b863f0f76de82a40d21e4a10bf3eabb3e /doc
parent6a67b3eb0c24994388e2ec4042ceea313c54334a (diff)
downloadvdebug-ff982623dc1d3c3df0f5c0de3f270c1c62a1820e.zip
Updated doc/Vdebug.txt for problems with php cli.
Diffstat (limited to 'doc')
-rw-r--r--doc/Vdebug.txt12
1 files changed, 10 insertions, 2 deletions
diff --git a/doc/Vdebug.txt b/doc/Vdebug.txt
index 93d6113..c6c4097 100644
--- a/doc/Vdebug.txt
+++ b/doc/Vdebug.txt
@@ -422,8 +422,8 @@ start a script in this way. It will be obvious when a connection is made,
because a new VIM tab opens with four windows, signalling the start of a new
debugging session.
-If you are starting a script but Vdebug does not react, see the
-|VdebugTroubleshooting| section for information.
+If you are starting a script but Vdebug does not react, or the source code is
+not loaded, see the |VdebugTroubleshooting| section for information.
The debugger will pause at the first line of the beginning of the script. It
then waits for your action before continuing.
@@ -1198,6 +1198,14 @@ the question is good I might even add it to this list.
Q. Why doesn't Ross, the largest friend, simply eat the other ones?
A. Think of the indigestion that would result.
+ Q. My command line php script seems to stop at the first line, but the
+ source code is not loaded in the debugger window, how can that be?
+ A. A possible solution is to launch vi in the directory, where your source
+ code resides.
+ Another possible issue was observed, when the source code was called
+ from within a bash script with 'php -r "<php code>". In this case, try
+ to put your source code in a separate .php file.
+
==============================================================================
11. Acknowledgements *VdebugAcknowledgements*