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 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 _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com