Issue Details (XML | Word | Printable)

Key: MODPYTHON-41
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Nicolas Lehuen
Reporter: Graham Dumpleton
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
mod_python

Calls to PyErr_Print should be followed by fflush().

Created: 28/Mar/05 06:58 PM   Updated: 05/Mar/06 01:49 PM
Component/s: core
Affects Version/s: 3.1.4
Fix Version/s: 3.2.7

Time Tracking:
Not Specified

Resolution Date: 30/Apr/05 04:06 PM


 Description  « Hide
In mod_python.c there are a few places where PyErr_Print() is called. The output of this
function is sent to stderr and not to the Apache log functions. The output does make its
way into the Apache error log file eventually, but not straight away due to buffering
issues. In order to ensure the output gets the logs straight away, a call should be made
to fflush(stderr) after calling PyErr_Print(). Ie.,

        PyErr_Print();
        fflush(stderr);

This will ensure that relevant lower level Python errors appear adjacent to any error message
logged by mod_python to the error log file.

 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.