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.

classification
Title: irreproducable segfault on int(1e100)
Type: Stage:
Components: Interpreter Core Versions: Python 2.3
process
Status: closed Resolution: not a bug
Dependencies: Superseder:
Assigned To: Nosy List: gerrit, loewis, rhettinger
Priority: normal Keywords:

Created on 2003-06-19 21:19 by gerrit, last changed 2022-04-10 16:09 by admin. This issue is now closed.

Messages (6)
msg16529 - (view) Author: Gerrit Holl (gerrit) Date: 2003-06-19 21:19
Segmentation Fault:

 20 >>> i
1e+100
 21 >>> int(i)Segmentation fault
23:16:12:2:gerrit@stopcontact:~/downl$ python
Python 2.3b1+ (#3, Jun 19 2003, 10:34:37)
[GCC 3.2.2 20030222 (Red Hat Linux 3.2.2-5)] on linux2
Type "help", "copyright", "credits" or "license" for
more information.
  0 >>> i=1e100
  1 >>> int(i)Segmentation fault
23:16:21:2:gerrit@stopcontact:~/downl$ python
Python 2.3b1+ (#3, Jun 19 2003, 10:34:37)
[GCC 3.2.2 20030222 (Red Hat Linux 3.2.2-5)] on linux2
Type "help", "copyright", "credits" or "license" for
more information.
  0 >>> i=1e100
  1 >>> int(i)
10000000000000000159028911097599180468360808563945281389781327557747838772170381060813469985856815104L

I'm unable to reproduce this (sorry). I noticed before
that sometimes, the interactive Python interpreter
segfaults irreproducable: only now, it was two times in
succession but not more than two times. I never
encounered this problem while executing Python programs
from scripts.
msg16530 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2003-06-21 13:44
Logged In: YES 
user_id=21627

I suspect this is a bug in the C library. To find out for
sure, one would have to study the relevant assembler code in
glibc in detail.
msg16531 - (view) Author: Raymond Hettinger (rhettinger) * (Python committer) Date: 2003-06-25 14:49
Logged In: YES 
user_id=80475

Under Windows compiled by MSVC++, I've run this hundred 
thousand times in a loop without a failure. I tried it in a 
script and using the interpreter, so it does appear to be 
specific to gcc.
msg16532 - (view) Author: Gerrit Holl (gerrit) Date: 2003-06-25 15:00
Logged In: YES 
user_id=13298

Interestingly, the problem does not occur within a script
here, too. Maybe it is in the readline library or something
like that. Pressing <shift>-<Enter> always segfaults for me
(known readline bug). This is the same as <Escape>-O-<Enter>
and the same problem is in Ruby and sh, so this is a
readline bug.  I think this because [int(1e100) for i in
xrange(1000000)] works fine, also on the interactive prompt.
Hmm, would there be a way to test this hypotesis?
msg16533 - (view) Author: Raymond Hettinger (rhettinger) * (Python committer) Date: 2003-07-01 05:05
Logged In: YES 
user_id=80475

I tried about 50 times with the interactive interpreter and 
got no failures.  Do you still have the same problem with a 
fresh download of the 2.3b2 release?  Can you post anything 
useful for tracking down the problem?   
msg16534 - (view) Author: Gerrit Holl (gerrit) Date: 2004-01-26 16:16
Logged In: YES 
user_id=13298

This bug is indeed invalid because it has nothing to do with
Python, it's a readline bug.
History
Date User Action Args
2022-04-10 16:09:20adminsetgithub: 38684
2003-06-19 21:19:46gerritcreate