Enabling Stack Traces in 2.6.1
Greetings, I'm a new Zope user, brought over by a friend (and soon-to-be coworker). I've been using Python for a while (~6 months or so). I ran into a problem last night that involved a Python script failing; the Zope error message referred to viewing the source of the page to view the stack trace, but there was no stack trace there; thinking that I had somehow misinstalled Zope on my Solaris (9) system, I installed Zope on my W2K box ... with exactly the same results. Aforementioned friend is scratching his head in puzzlement, so I figured I'd post and ask if I'm missing something obvious in trying to get access to the stack trace. -roy
Roy S. Rapoport wrote:
Aforementioned friend is scratching his head in puzzlement, so I figured I'd post and ask if I'm missing something obvious in trying to get access to the stack trace.
they should be captured in the /error_log object which you can examine through the ZMI -- Jamie Heilman http://audible.transient.net/~jamie/ "Most people wouldn't know music if it came up and bit them on the ass." -Frank Zappa
On Sun, Jul 06, 2003 at 01:23:09PM -0700, Jamie Heilman wrote:
Roy S. Rapoport wrote:
Aforementioned friend is scratching his head in puzzlement, so I figured I'd post and ask if I'm missing something obvious in trying to get access to the stack trace.
they should be captured in the /error_log object which you can examine through the ZMI
Thanks! This does indeed give me the stack trace. Does this mean that as of 2.6.1 or sometime a little earlier Zope can't give you the stack trace in the error message it shows? -roy
Roy S. Rapoport wrote:
Thanks! This does indeed give me the stack trace. Does this mean that as of 2.6.1 or sometime a little earlier Zope can't give you the stack trace in the error message it shows?
No, it can, thats the error_tb variable, its just not recommended. -- Jamie Heilman http://audible.transient.net/~jamie/ "...thats the metaphorical equivalent of flopping your wedding tackle into a lion's mouth and flicking his lovespuds with a wet towel, pure insanity..." -Rimmer
I ran into a problem last night that involved a Python script failing; the Zope error message referred to viewing the source of the page to view the stack trace, but there was no stack trace there;
This message "view page source etc" is like a bad joke - i've looking at HTML page source several times before i understood that author of this message really mean "if you're site adminitsrator, look at DTML-source of a document which produces error" or something like that. Maybe we need more user (read -"site visitor")-friendly message? The current one seems very ambiguous and frustrating. Can it be considered as a bug and posted into Collector?
I ran into a problem last night that involved a Python script failing; the Zope error message referred to viewing the source of the page to view the stack trace, but there was no stack trace there;
This message "view page source etc" is like a bad joke - i've looking at HTML page source several times before i understood that author of this message really mean "if you're site adminitsrator, look at DTML-source of a document which produces error" or something like that.
Maybe we need more user (read -"site visitor")-friendly message? The current one seems very ambiguous and frustrating. Can it be considered as a bug and posted into Collector?
Actually, it's a historical artifact from when the stack traces *were* included in the HTML source of the error page. Which, while a different problem, is still a problem. Please file a bug (or make a little noise on zope-dev.) --jcc
participants (4)
-
J Cameron Cooper -
Jamie Heilman -
Roy S. Rapoport -
Sergey Volobuev