Bugs item #1745108, was opened at 2007-06-29 00:13
Message generated for change (Comment added) made by maswan
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1745108&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: Extension Modules
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Mattias Wadenstein (maswan)
Assigned to: Nobody/Anonymous (nobody)
Summary: 2.5.1 curses panel segfault in new_panel on aix 5.3
Initial Comment:
I've compiled python 2.5.1 on AIX 5.3 with ncurses 5.6 and I get segmentation
faults as soon as any curses.panel tries to make a new panel.
The following test program gives a segmentation fault for me (remove the
new_panel line and it works fine):
import curses
from curses import panel
def mkpanel(scr):
win = curses.newwin(8,8,1,1)
pan = panel.new_panel(win)
curses.wrapper(mkpanel)
Also the test_curses program triggers this segfault. A traceback puts the
problem in:
root_panel(), line 57 in "p_new.c"
new_panel(win = 0x0000000110246dc0), line 90 in "p_new.c"
PyCurses_new_panel(self = (nil), args = 0x0000000110246dc0), line 396 in
"_curses_panel.c"
PyCFunction_Call(func = 0x000000011024a368, arg = 0x0000000110246dc0, kw =
(nil)), line 73 in "methodobject.c"
Note that the ncurses I've compiled works fine with the shipped test programs,
so it seems to be an issue with the python interaction.
Please let me know if there is anything else that I can provide to help track
this bug down.
----------------------------------------------------------------------
>Comment By: Mattias Wadenstein (maswan)
Date: 2007-07-03 08:12
Message:
Logged In: YES
user_id=1831392
Originator: YES
We'll look into the issue of temporarily giving someone access, but it is
somewhat problematic.
Some answers until then:
* Same behaviour on both 32-bit and 64-bit
* Compiled with xlc v8.0
* I will try and set gcc up
* Same behaviour with or without optimization, debug flags, etc (just
slightly different backtraces, less verbose without debug symbols)
* Same thing --with-pydebug or without, just slightly different output
* I'll look, but nothing comes to mind right now
----------------------------------------------------------------------
Comment By: Neal Norwitz (nnorwitz)
Date: 2007-07-03 06:21
Message:
Logged In: YES
user_id=33168
Originator: NO
No python developer has access to AIX AFAIK. So you will likely need to
debug this problem yourself or provide access to an AIX box. Here are some
questions to get you started:
* Does this problem happen as a 32-bit exe rather than 64-bit?
* Did you use xlc, gcc, or some other compiler?
* What happens if you switch compilers?
* Does this happen if you disable optimization?
* What happens if you build a debug version of python (./configure
--with-pydebug)?
* Do you have any memory debugging tool that you can use to track this
down?
It looks like there is a problem derefencing a function pointer. I don't
know why that might happen.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1745108&group_id=5470
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
