[Zope-Coders] Re: [Zope] Reclaim the Stupid Logfile Traceback Format!

[Chris Withers]

<taking this back onto the lists to find out what the story is>

Johan Carlsson [EasyPublisher] wrote:
> At 18:21 2002-12-05 +0000, Chris Withers said:
> 
>> Johan Carlsson [EasyPublisher] wrote:
>>
>>>>> Now I get file pointers in the Stupid Log File (not in the web 
>>>>> traceback)
>>>>
>>>> What do you mean by 'file pointers'?
>>>
>>> Path + line number into the file where the error occurred.
>>> I'm not really sure what to call them :-)
>>
>> Weird they only show up in the log file. Maybe ask on zope-coders 
>> ayway to find out
>> whether this is intentional or not. Seems a bit unhelpful to me...
> 
> I think it is intentional.

Well, Shane said it wasn't. I think it's a bad idea in any case. The 
format_exception in zLOG, unless I'm verymuch mistaken, should include the full 
traceback, which in 2.6.1b1 it doesn't :-(

> Note that I haven't tried how a plain -D/std_out looks, it will probably 
> look ok)

It shouldn't make a difference in this case. If you get an unexpected exception 
on a production system it's even mroe critical to grab as much info as possible.

> What doesn't work is the web interface, in which case the use of knowing
> the full path or either if it's a good thing from a security?

Not sure what you mean here...

I'm still confused as to why some exceptions are missing tracebacks and others 
aren't. I'm even more worried 'cos 2.6.1b1 is exhibiting this behaviour and I 
don't want to have to wait until 2.6.2 to get it fixed :-(

Help!

Chris