[ python-Bugs-687297 ] Profilier hooked into SystemExit

[SourceForge.net]

Bugs item #687297, was opened at 2003-02-15 22:41
Message generated for change (Comment added) made by facundobatista
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=687297&group_id=5470

Category: Demos and Tools
Group: Python 2.2.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Dylan Shell (dshell)
Assigned to: Nobody/Anonymous (nobody)
Summary: Profilier hooked into SystemExit

Initial Comment:
I've been attempting to profile code that uses the
PyOpenGL bindings. Essentially I've got a program with
that calls glutMainLoop - which is said to never return.

The problem is that since this really envokes some C
code that calls "exit" the profiler does not catch a
"SystemExit" exception, because this is never thrown.

If there was a way to get the profiler to dump state on
demand, I could do this in an "onExit" event handler,
and then restart python with the pstats module to have
a look-see.

Alternatively the profiler could use some OS provided
exit handler - or something simliar.

Also, running the main loop in a thread does not seem
to work (the video memory used by GLUT) is corrupted.
So, this isn't a fair test on which to profile.

I suspect that the ability to dump profile stats to
disk could also be useful for other folks.




----------------------------------------------------------------------

Comment By: Facundo Batista (facundobatista)
Date: 2005-01-11 01:08

Message:
Logged In: YES 
user_id=752496

Please, could you verify if this problem persists in Python 2.3.4
or 2.4?

If yes, in which version? Can you provide a test case?

If the problem is solved, from which version?

Note that if you fail to answer in one month, I'll close this bug
as "Won't fix".

Thank you! 

.    Facundo

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=687297&group_id=5470