This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Segmentation fault when importing expat from xml.parser
Type: Stage:
Components: XML Versions: Python 2.4
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: bernhard, georg.brandl, jean-pierre24, nnorwitz, sf-robot
Priority: normal Keywords:

Created on 2005-07-27 23:07 by jean-pierre24, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
backtrace.txt jean-pierre24, 2005-07-27 23:07 backtrace from gdb
valgrind.log jean-pierre24, 2005-10-06 20:23 output of valgrind
Messages (8)
msg25878 - (view) Author: Jean-Pierre (jean-pierre24) Date: 2005-07-27 23:07
 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...
msg25879 - (view) Author: Neal Norwitz (nnorwitz) * (Python committer) Date: 2005-10-04 05:10
Logged In: YES 
user_id=33168

Can you provide a link to the wx bug report?  Has anything
happend with it?
msg25880 - (view) Author: Jean-Pierre (jean-pierre24) Date: 2005-10-04 22:05
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.
msg25881 - (view) Author: Neal Norwitz (nnorwitz) * (Python committer) Date: 2005-10-05 03:34
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.
msg25882 - (view) Author: Jean-Pierre (jean-pierre24) Date: 2005-10-06 20:23
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.
msg25883 - (view) Author: Bernhard Herzog (bernhard) Date: 2005-12-01 13:51
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
msg25884 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2006-07-29 10:36
Logged In: YES 
user_id=849994

Patch 1295808 should have fixed this. Can you try it with
Python 2.5b2?
msg25885 - (view) Author: SourceForge Robot (sf-robot) Date: 2006-08-13 02:20
Logged In: YES 
user_id=1312539

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
History
Date User Action Args
2022-04-11 14:56:12adminsetgithub: 42225
2005-07-27 23:07:11jean-pierre24create