[ python-Bugs-1607759 ] segfault in python24.dll

[SourceForge.net]

Bugs item #1607759, was opened at 2006-12-03 10:18
Message generated for change (Comment added) made by etaoinbe2
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1607759&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: Python Library
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: joe (etaoinbe2)
Assigned to: Nobody/Anonymous (nobody)
Summary: segfault in python24.dll

Initial Comment:
In my app that uses wxpython2.7 extensively I get regularly following segfault (null pointer exception): 

AppName: python.exe	 AppVer: 0.0.0.0	 ModName: python24.dll
ModVer: 2.4.150.1012	 Offset: 00030f33

I have been unable to pinpoint it to a certain location of the program. :( 



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

>Comment By: joe (etaoinbe2)
Date: 2006-12-03 18:42

Message:
Logged In: YES 
user_id=1249766
Originator: YES

I have vs7.0 & 6.0
7.0 does not accept 7.1 project files
so try with 6.0 : 
--------------------Configuration: pythoncore - Win32
Debug--------------------
Build : warning : failed to (or don't know how to) build
'C:\Python-2.5\Modules\structmodule.c'
Compiling...
exceptions.c
fatal error C1083: Cannot open source file:
'C:\Python-2.5\Python\exceptions.c': No such file or directory
md5c.c
fatal error C1083: Cannot open source file:
'C:\Python-2.5\Modules\md5c.c': No such file or directory
structmodule.c
fatal error C1083: Cannot open source file:
'C:\Python-2.5\Modules\structmodule.c': No such file or directory
Error executing cl.exe.

python25_d.dll - 3 error(s), 1 warning(s)

Those files are really not there ? So how shall I proceed ?


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

Comment By: Martin v. Löwis (loewis)
Date: 2006-12-03 13:56

Message:
Logged In: YES 
user_id=21627
Originator: NO

For a debug build, you need debug versions of everything, including
wxPython.

If you have VS.NET 2003 or 2005, you should be able to produce such
binaries yourself. For Python, you need to follow the instructions in
PCBuild/readme.txt. I don't know how wxPython is built.

You might also be successful with creating a release build that has debug
information enabled; in that case, it is sufficient to rebuild Python.

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

Comment By: joe (etaoinbe2)
Date: 2006-12-03 13:10

Message:
Logged In: YES 
user_id=1249766
Originator: YES

I have tried to insulate the problem to a particular part of the code but
that did not work out. I have currently no small program that shows this
only the complete integrated app shows this. 

If you have a build with assembler listings enabled then you might be able
to find where that address is ? 

Or can I get a debugbuild so that a meaningfull stacktrace can be
produced?

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

Comment By: Martin v. Löwis (loewis)
Date: 2006-12-03 10:36

Message:
Logged In: YES 
user_id=21627
Originator: NO

AFAICT, this might be a bug in wxpython also, or in some other extension
module you are using.

Can you give any example code that allows to reproduce the crash? Without
that, there is little chance that the problem can be fixed.

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

Comment By: joe (etaoinbe2)
Date: 2006-12-03 10:25

Message:
Logged In: YES 
user_id=1249766
Originator: YES

this is on windows, the faulting address is always the same

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

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