Profilier hooked into SystemExit

[dshell]

BPO	687297
Nosy	@facundobatista

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2005-05-30.19:47:28.000>
created_at = <Date 2003-02-16.01:41:48.000>
labels = []
title = 'Profilier hooked into SystemExit'
updated_at = <Date 2005-05-30.19:47:28.000>
user = 'https://bugs.python.org/dshell'

bugs.python.org fields:

activity = <Date 2005-05-30.19:47:28.000>
actor = 'facundobatista'
assignee = 'none'
closed = True
closed_date = None
closer = None
components = ['Demos and Tools']
creation = <Date 2003-02-16.01:41:48.000>
creator = 'dshell'
dependencies = []
files = []
hgrepos = []
issue_num = 687297
keywords = []
message_count = 3.0
messages = ['14612', '14613', '14614']
nosy_count = 2.0
nosy_names = ['facundobatista', 'dshell']
pr_nums = []
priority = 'normal'
resolution = 'wont fix'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue687297'
versions = ['Python 2.2']

[dshell]

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.

[facundobatista]

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

[facundobatista]

Logged In: YES
user_id=752496

Deprecated. Reopen only if still happens in 2.3 or newer.

. Facundo