[ python-Bugs-1246405 ] Segmentation fault when importing expat from xml.parser

[SourceForge.net]

Bugs item #1246405, was opened at 2005-07-28 01:07
Message generated for change (Comment added) made by bernhard
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1246405&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: XML
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Jean-Pierre (jean-pierre24)
Assigned to: Nobody/Anonymous (nobody)
Summary: Segmentation fault when importing expat from xml.parser

Initial Comment:
 Hello,

I have a strange segmentation fault when importing
expat from xml.parsers in the following program (I
removed all that is un-necessary to reproduce the bug,
which is why the code may look odd).

I've also posted this bug on wxPython bug lists because
I'm not sure if it's related to Python or wxPython, but
anyway the backtrace told me that the segmentation
fault occurs when importing expat.

import wx
import wx.html

class MainFrame(wx.Frame):
def __init__(self, prnt):
wx.Frame.__init__(self, parent=prnt)
wx.html.HtmlWindow(wx.Window(self, -1), -1)
print "debug 1"
from xml.parsers import expat
print "debug 2"

class BoaApp(wx.App):
def OnInit(self):
wx.InitAllImageHandlers()
MainFrame(None)
return True

app = BoaApp()

The segmentation fault occurs between 'debug 1' and
'debug 2'. If I try to remove anything else, it doesn't
happen.
I have confirmed the bug on SunOS 5.8, on linux Red Hat
Enterprise Server 3 and linux Advanced Server 3.
I'm working with Python 2.4.1 and wxPython 2.6.1.0
Here is in attached file, the backtrace from gdb.

Feel free to ask me any additional information...


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

Comment By: Bernhard Herzog (bernhard)
Date: 2005-12-01 14:51

Message:
Logged In: YES 
user_id=2369

Could this be the same problem as bug 1075984 ?
URL:
https://sourceforge.net/tracker/index.php?func=detail&aid=1075984&group_id=5470&atid=105470


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

Comment By: Jean-Pierre (jean-pierre24)
Date: 2005-10-06 22:23

Message:
Logged In: YES 
user_id=1247525

Yes I can try with different version of wx, but it will take
time.
Anyway for today here is in attachment the valgrind output
on linux x86.

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

Comment By: Neal Norwitz (nnorwitz)
Date: 2005-10-05 05:34

Message:
Logged In: YES 
user_id=33168

I don't have the problem with Python 2.3.4 and wx 2.5.5.1.

Are you able to try different versions of wxPython?  I
notice that wx 2.6.2 is available.  Are you able to run
under valgrind or purify?

If you run under valgrind, be sure to specify
--suppressions=Misc/valgrind-python.supp
The file is in the Python distribution.  You can download it
through SourceForge ViewCVS.

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

Comment By: Jean-Pierre (jean-pierre24)
Date: 2005-10-05 00:05

Message:
Logged In: YES 
user_id=1247525

Link is :
http://sourceforge.net/tracker/index.php?func=detail&aid=1246397&group_id=9863&atid=109863

Unfortunately, absolutely nothing has happened since I
reported the bug.

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

Comment By: Neal Norwitz (nnorwitz)
Date: 2005-10-04 07:10

Message:
Logged In: YES 
user_id=33168

Can you provide a link to the wx bug report?  Has anything
happend with it?

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

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