no traceback??

Tim Hammerquist tim at vegeta.ath.cx
Mon Jul 23 09:49:12 CEST 2001


Me parece que Rainy <sill at optonline.net> dijo:
> Well, I'm asking in a general way, i.e. why could there be no traceback or
> error? This is not right. I mean, if a program runs into a problem, it should
> print some sort of feedback, at worst, a segfault? I haven't run into cases
> like this before when *NOTHING* is printed. In general, what sort of errors
> just quit silently?

I would guess that it _is_ raising an exception, but it's caught at some
point up in the call chain by an 'except: pass' clause.  What happens
right before the invisible error?  What is it doing at that point?

-- 
C combines all the power of assembly language with all
the ease of use of assembly language.
    -- trad



More information about the Python-list mailing list