Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Z
Zope
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
Zope
Commits
bc666f6e
Commit
bc666f6e
authored
Feb 20, 2009
by
Andreas Jung
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
DEBUGGING
parent
65ef3bf3
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
18 additions
and
15 deletions
+18
-15
doc/DEBUGGING.txt
doc/DEBUGGING.txt
+17
-15
doc/index.txt
doc/index.txt
+1
-0
No files found.
doc/DEBUGGING.txt
View file @
bc666f6e
Running Zope in Debug Mode
Running Zope in Debug Mode
==========================
If you wish to run Zope in debug mode, set the 'debug-mode'
If you wish to run Zope in debug mode, set the 'debug-mode'
configuration file parameter to 'on' (this is the default). This
configuration file parameter to 'on' (this is the default). This
will have the following effects:
:
will have the following effects
:
o
On UNIX, Zope will not detach from the controlling terminal.
-
On UNIX, Zope will not detach from the controlling terminal.
o
The Z_DEBUG_MODE environment variable gets set, which causes
-
The Z_DEBUG_MODE environment variable gets set, which causes
behavioral changes to Zope appropriate for software development.
behavioral changes to Zope appropriate for software development.
See the configuration file description of 'debug-mode' for more
See the configuration file description of 'debug-mode' for more
information.
information.
Using 'zopectl debug'
Using 'zopectl debug'
---------------------
A utility known as 'zopectl' is installed into generated instance homes.
A utility known as 'zopectl' is installed into generated instance homes.
You can use it to inspect a Zope instance's running state via an
You can use it to inspect a Zope instance's running state via an
interactive Python interpreter by passing zopectl the 'debug' parameter
interactive Python interpreter by passing zopectl the 'debug' parameter
on the command line. The 'top-level' Zope object (the root folder) will
on the command line. The 'top-level' Zope object (the root folder) will
be bound to the name 'app' within the interpreter. You can then use
be bound to the name 'app' within the interpreter. You can then use
normal Python method calls against app and use the Python interpreter
normal Python method calls against app and use the Python interpreter
normally to inspect results::
normally to inspect results::
[chrism@james Trunk]$ bin/zopectl debug
[chrism@james Trunk]$ bin/zopectl debug
Starting debugger (the name "app" is bound to the top-level Zope object)
Starting debugger (the name "app" is bound to the top-level Zope object)
...
...
doc/index.txt
View file @
bc666f6e
...
@@ -16,6 +16,7 @@ Contents:
...
@@ -16,6 +16,7 @@ Contents:
ZOPE3.txt
ZOPE3.txt
SETUID.txt
SETUID.txt
SIGNALS.txt
SIGNALS.txt
DEBUGGING.txt
CREDITS.txt
CREDITS.txt
Indices and tables
Indices and tables
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment