[issue1745108] 2.5.1 curses panel segfault in new_panel on aix 5.3

2015-04-14 Thread A.M. Kuchling
A.M. Kuchling added the comment: Closing this ticket as outdated; AIX 5.3 is from 2004. -- nosy: +akuchling resolution: -> wont fix stage: -> resolved status: open -> closed ___ Python tracker _

[issue1745108] 2.5.1 curses panel segfault in new_panel on aix 5.3

2014-12-31 Thread A.M. Kuchling
Changes by A.M. Kuchling : -- nosy: -akuchling ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue1745108] 2.5.1 curses panel segfault in new_panel on aix 5.3

2014-07-21 Thread Mark Lawrence
Changes by Mark Lawrence : -- nosy: +David.Edelsohn type: -> crash versions: +Python 2.7, Python 3.4, Python 3.5 ___ Python tracker ___ ___

[issue1745108] 2.5.1 curses panel segfault in new_panel on aix 5.3

2010-11-12 Thread A.M. Kuchling
Changes by A.M. Kuchling : -- assignee: akuchling -> ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue1745108] 2.5.1 curses panel segfault in new_panel on aix 5.3

2010-09-14 Thread Sébastien Sablé
Changes by Sébastien Sablé : -- nosy: +sable ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue1745108] 2.5.1 curses panel segfault in new_panel on aix 5.3

2008-01-21 Thread A.M. Kuchling
A.M. Kuchling added the comment: I don't see how win->win could be uninitialized. curses.newwin() creates a PyCursesWindowObject using PyCursesWindow_New(), which always fills in the ->win field. I'm puzzled by the 2007-06-28 traceback. Pycurses_new_panel has args = 0x000110246dc0; args s

[issue1745108] 2.5.1 curses panel segfault in new_panel on aix 5.3

2007-12-26 Thread Paul Smedley
Paul Smedley added the comment: I see similar problems here on OS/2 with Python 2.5.1 and Ncurses 5.6. Problem is causes as win->win is uninitialised when passed to new_panel. Initialising win->win to a value makes the new_panel call work. Not sure why this works on other platforms but fails o