readline problem on ia64-unknown-linux-gnu

[kate01123]

BPO	1593035
Nosy	@akuchling, @terryjreedy

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2010-06-17.01:13:55.752>
created_at = <Date 2006-11-08.23:48:54.000>
labels = ['interpreter-core']
title = 'readline problem on ia64-unknown-linux-gnu'
updated_at = <Date 2010-06-17.01:13:55.750>
user = 'https://bugs.python.org/kate01123'

bugs.python.org fields:

activity = <Date 2010-06-17.01:13:55.750>
actor = 'terry.reedy'
assignee = 'none'
closed = True
closed_date = <Date 2010-06-17.01:13:55.752>
closer = 'terry.reedy'
components = ['Interpreter Core']
creation = <Date 2006-11-08.23:48:54.000>
creator = 'kate01123'
dependencies = []
files = []
hgrepos = []
issue_num = 1593035
keywords = []
message_count = 4.0
messages = ['61032', '61033', '73943', '107978']
nosy_count = 4.0
nosy_names = ['akuchling', 'terry.reedy', 'kate01123', 'henry.precheur']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue1593035'
versions = ['Python 2.5']

[kate01123]

On my ia64-unknown-linux-gnu machine, running
python-2.5, if I import the following code (foo.py) and
then try to do file name completion, I get a
segmentation fault. Specifically, if after importing
foo.py, if I type "im" and then [tab], I get a
segmentation fault.

I built python-2.5 from source using the default
values. (All I did was "configure", then "make".)

This does NOT happen under python-2.4.4.

----- foo.py ------
try:
import rlcompleter,readline
except ImportError:
print '*** No readline support ***'
pass
else:
readline.set_history_length(1000)
# parse and bind all these:
rlcmds = ['tab: complete',
r'"\M-p": history-search-backward',
r'"\M-n": history-search-forward',
r'"\C-p": history-search-backward',
r'"\C-n": history-search-forward',
r'"\e[A": history-search-backward',
r'"\e[B": history-search-forward',
'set show-all-if-ambiguous on',
]
map(readline.parse_and_bind,rlcmds)
-----------------------

%uname -a
Linux lepidus 2.4.21-sgi302r24 #1 SMP Fri Oct 22
22:43:12 PDT 2004 ia64 ia64 ia64 GNU/Linux
%
% ./python --version
Python 2.5
% 
% ./python 
Python 2.5 (r25:51908, Nov  8 2006, 15:40:13)
[GCC 4.1.1] on linux2
Type "help", "copyright", "credits" or "license" for
more information.
>>> import foo
>>> impSegmentation fault (core dumped)
%
% gdb ./python
GNU gdb Red Hat Linux (6.0post-0.20040223.20rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public
License, and you are
welcome to change it and/or distribute copies of it
under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show
warranty" for details.
This GDB was configured as
"ia64-redhat-linux-gnu"...Using host libthread_db library
"/lib/tls/libthread_db.so.1".

(gdb) r
Starting program: /home/kate/sage/william/Python-2.5/python
[Thread debugging using libthread_db enabled]
[New Thread 2305843009213881680 (LWP 23166)]
Python 2.5 (r25:51908, Nov  8 2006, 15:40:13)
[GCC 4.1.1] on linux2
Type "help", "copyright", "credits" or "license" for
more information.
>>> import foo
>>> im
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 2305843009213881680 (LWP 23166)]
0x200000000264ae90 in rl_complete_internal () from
/usr/lib/libreadline.so.4
(gdb) bt
#0  0x200000000264ae90 in rl_complete_internal () from
/usr/lib/libreadline.so.4
#1  0x2000000002646d90 in rl_complete () from
/usr/lib/libreadline.so.4
#2  0x200000000263bc40 in _rl_dispatch_subseq () from
/usr/lib/libreadline.so.4
#3  0x200000000263b780 in _rl_dispatch () from
/usr/lib/libreadline.so.4
#4  0x200000000263af90 in readline_internal_char ()
from /usr/lib/libreadline.so.4
#5  0x0000000000000000 in ?? ()
(gdb)

Kate Minola
University of Maryland, College Park

[akuchling]

I wonder if this crash is related to the function pointer issue described in
bug bpo-1597798.

[henryprecheur]

This problem was probably solved in issue bpo-1204.

[terryjreedy]

In the absence of a claim otherwise, I am assuming that this is now either fixed or out-of-date