Pygame catches the signal the kernel sends to kill a process when the process has been naughty... (Think seg faults, for example.) Why the authors of pygame did that rather than letting the process die normally, I'm not sure. But, it appears that there's code in the source of pygame to attempt to show the python traceback, which is disabled with the comment "this traceback hacking has gotten a bit treacherous". You could attempt to print tracebacks by fiddling with that code and recompiling pygame, but I always find it easier to bisect my code with print statements. Ariel Rokem wrote: > Hello - can anyone tell me what a "pygame parachute" is? > > Thanks -- > > Ariel > > ------------------------------------------------------ > Ariel Rokem > Helen Wills Neuroscience Institute > 582 Minor Hall > University of California, Berkeley > Berkeley, CA 94720-2020 > -- > Tel: +1-510-6423134 > -- > http://argentum.ucbso.berkeley.edu/ariel > ------------------------------------------------------ > > ====================================== > The Vision Egg mailing list > Archives: //www.freelists.org/archives/visionegg > Website: http://www.visionegg.org/mailinglist.html -- Dr. Andrew D. Straw California Institute of Technology http://www.its.caltech.edu/~astraw/ ====================================== The Vision Egg mailing list Archives: //www.freelists.org/archives/visionegg Website: http://www.visionegg.org/mailinglist.html