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.

Title: curses test_curses.test_unget_wch crash
Type: Stage: resolved
Components: Library (Lib) Versions: Python 3.3
Status: closed Resolution: duplicate
Dependencies: Superseder: curses.unget_wch and test_curses fail when linked with ncurses 5.7 and earlier
View: 15037
Assigned To: Nosy List: chris.jerdonek, ned.deily
Priority: normal Keywords:

Created on 2012-09-03 00:39 by chris.jerdonek, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (4)
msg169734 - (view) Author: Chris Jerdonek (chris.jerdonek) * (Python committer) Date: 2012-09-03 00:39
As of: changeset:   78843:8ff2f4634ed8
date:        Sun Sep 02 16:37:09 2012 -0400

I am getting this failure:

$ ./python.exe -m test -v -u curses test_curses
== CPython 3.3.0rc1+ (default:8ff2f4634ed8, Sep 2 2012, 16:02:43) [GCC 4.2.1 Compatible Apple Clang 3.1 (tags/Apple/clang-318.0.58)]
==   Darwin-11.4.0-x86_64-i386-64bit little-endian
==   .../build/test_python_17427
Testing with flags: sys.flags(debug=0, inspect=0, interactive=0, optimize=0, dont_write_bytecode=0, no_user_site=0, no_site=0, ignore_environment=0, verbose=0, bytes_warning=0, quiet=0, hash_randomization=1)
[1/1] test_curses
test test_curses crashed -- Traceback (most recent call last):
  File ".../Lib/test/", line 1221, in runtest_inner
  File ".../Lib/test/", line 336, in test_main
  File ".../Lib/test/", line 322, in main
  File ".../Lib/test/", line 283, in test_unget_wch
    raise AssertionError("%r != %r" % (read, ch))
AssertionError: -61 != 'é'

Looks like this may be related to issue 15785.
msg169740 - (view) Author: Ned Deily (ned.deily) * (Python committer) Date: 2012-09-03 04:39
This is a duplicate of Issue15037.  test_unget_wch fails when linked with ncurses versions earlier than 5.8, which is the case with the Apple-supplied versions of ncurses in OS X versions through 10.8.  (The OS X installers for Python 3.3.x link with their own copy of libncursesw 5.9 to avoid this problem.)
msg169741 - (view) Author: Chris Jerdonek (chris.jerdonek) * (Python committer) Date: 2012-09-03 04:44
Okay, thanks, Ned.  Out of curiosity, why is the stack trace here different from the one posted on that issue?
msg169742 - (view) Author: Ned Deily (ned.deily) * (Python committer) Date: 2012-09-03 04:57
Different version of libncurses, different compiler and run time, different version and build options of Python 3.3, etc. The bug in ncurses causes junk to be stored and/or returned.  In the one case, the junk triggered an overflow error, in the other, no overflow but still junk.
Date User Action Args
2022-04-11 14:57:35adminsetgithub: 60058
2012-09-03 04:57:37ned.deilysetmessages: + msg169742
2012-09-03 04:44:41chris.jerdoneksetmessages: + msg169741
2012-09-03 04:39:53ned.deilysetstatus: open -> closed

superseder: curses.unget_wch and test_curses fail when linked with ncurses 5.7 and earlier
nosy: + ned.deily

messages: + msg169740
type: crash ->
resolution: duplicate
stage: resolved
2012-09-03 00:40:35chris.jerdoneksettitle: curses test_curses test_unget_wch -> curses test_curses.test_unget_wch crash
2012-09-03 00:39:54chris.jerdonekcreate