Red Hat Bugzilla – Bug 200262
Segfault in hotshot profiler
Last modified: 2008-08-02 19:40:33 EDT
Description of problem:
I occasionally get a segfault in a Python script that I have. I've run it under
gdb and grabbed backtrace, and it appears that the hotshot profiler is the culprit.
Version-Release number of selected component (if applicable):
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 4035831008 (LWP 11180)]
profiler_callback (self=0x1e203b30, frame=0x1d2cbd70, what=3, arg=Variable "arg"
is not available.
) at /usr/src/debug/Python-2.3.4/Modules/_hotshot.c:582
582 self->buffer[self->index] = partial;
Created attachment 133078 [details]
Have a reproducer for this? The backtrace isn't all that enlightening at a glance
Closing due to inactivity; please reopen if you have further information to add
to this report.