Bug 118933

Summary: PDB browse from gimp causes "Segmentation fault"
Product: [Fedora] Fedora Reporter: Michal Jaegermann <michal>
Component: gimpAssignee: Nils Philippsen <nphilipp>
Status: CLOSED RAWHIDE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhide   
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: 2004-04-06 20:54:50 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:
Bug Depends On:    
Bug Blocks: 114963    
Attachments:
Description Flags
backtrace from a crash of Python-Fu none

Description Michal Jaegermann 2004-03-22 22:54:26 UTC 
Description of problem:

A use of "PDB browser" after looking at some number of entries
produced "Segmentation fault" with an attached backtrace
(rather long - 81 levels).  I am not sure which steps really led
that it.

Version-Release number of selected component (if applicable):
gimp-2.0-1.pre3.4.1

How reproducible:
I was unable reproduce in a deliberate manner.
Comment 1 Michal Jaegermann 2004-03-22 22:56:15 UTC 
Created attachment 98762 [details]
backtrace from a crash of  Python-Fu
Comment 2 Nils Philippsen 2004-04-05 21:11:33 UTC 
Can you please verify this with gimp-2.0.0-5?
Comment 3 Michal Jaegermann 2004-04-05 21:29:13 UTC 
I already tried and so far I failed to make it croak.  OTOH
I do not know really how I managed to get it to fail in the first
place, and my hope was that a backtrace will provide at least
some information to a person familiar with internals, but scripts
now seem to be in a better shape in general.
Comment 4 Nils Philippsen 2004-04-06 20:54:50 UTC 
Well, upstream does the bugfixing for a reason ;-). I'll close this
for now, if it happens again, reopen it.