[Python-bugs-list] [Bug #115844] OverflowError: integer multiplication

noreply@sourceforge.net noreply@sourceforge.net
Tue, 3 Oct 2000 11:17:57 -0700


Bug #115844, was updated on 2000-Oct-02 06:27
Here is a current snapshot of the bug.

Project: Python
Category: Core
Status: Open
Resolution: None
Bug Group: Platform-specific
Priority: 6
Summary: OverflowError: integer multiplication

Details: 
Python2.0b2 compiled from source on a full RH7.0 install:


Python 2.0b2 (#2, Sep 27 2000, 11:40:58) 
[GCC 2.96 20000731 (Red Hat Linux 7.0)] on linux2
Type "copyright", "credits" or "license" for more information.
>>> a = 5 * 5
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
OverflowError: integer multiplication
>>>

Follow-Ups:

Date: 2000-Oct-02 06:39
By: gvanrossum

Comment:
Something very basic is wrong. What output does the test suite give? ("make test"). Please see the README for digging into this.

Note that you submitted your bug report anonymously. We can't help you very effectively unless we can exchange email with you!
-------------------------------------------------------

Date: 2000-Oct-03 08:27
By: jhylton

Comment:
Strange! Another bug about integer multiplication overflow.  The other one is on a Debian install.

-------------------------------------------------------

Date: 2000-Oct-03 10:21
By: gvanrossum

Comment:
Could it be a 64-bit bug? Otherwise I suspect a GCC bug, or a 64-bit GCC bug. Note that GCC 2.96 is bleeding edge!
-------------------------------------------------------

Date: 2000-Oct-03 10:30
By: fdrake

Comment:
I don't see any reference to GCC 2.96 on the GCC website (http://gcc.gnu.org/).  PythonLabs should be a RH7.0 box to perform testing.

This may be a duplicate of #1159191.
-------------------------------------------------------

Date: 2000-Oct-03 11:17
By: jhylton

Comment:
This bug has also been reported on a system using gcc2.95, so I'm going try with that version of GCC.  It doesn't sound like this is a 64-bit platform; does RH7 run on a 64-bit platform?  It does appear that the problem is caused by LONG_BIT being too big resulting in a bogus shift.

-------------------------------------------------------

For detailed info, follow this link:
http://sourceforge.net/bugs/?func=detailbug&bug_id=115844&group_id=5470