Bug 200262

Summary:

Segfault in hotshot profiler

Product:

Red Hat Enterprise Linux 4

Reporter:

Dennis Gregorovic <dgregor>

Component:

python

Assignee:

James Antill <james.antill>

Status:

CLOSED INSUFFICIENT_DATA

QA Contact:

Brock Organ <borgan>

Severity:

medium

Docs Contact:

Priority:

medium

Version:

4.0

CC:

katzj

Target Milestone:

---

Target Release:

---

Hardware:

All

OS:

Linux

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2008-06-13 17:29:30 UTC

Type:

---

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Attachments:

Description	Flags
backtrace	none

Description Dennis Gregorovic 2006-07-26 15:48:42 UTC

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):
python-2.3.4-14.2

How reproducible:
Sometimes

Additional info:

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;

Comment 1 Dennis Gregorovic 2006-07-26 15:49:50 UTC

Created attachment 133078 [details]
backtrace

Comment 2 Jeremy Katz 2007-01-06 21:24:36 UTC

Have a reproducer for this?  The backtrace isn't all that enlightening at a glance

Comment 3 Jeremy Katz 2008-06-13 17:29:30 UTC

Closing due to inactivity; please reopen if you have further information to add
to this report.