2.2 on HP-UX 11 64-bit - longs crash

[scav]

BPO	533632
Nosy	@tim-one, @loewis

^{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 2002-03-25.08:43:52.000>
created_at = <Date 2002-03-22.15:43:49.000>
labels = []
title = '2.2 on HP-UX 11 64-bit - longs crash'
updated_at = <Date 2002-03-25.08:43:52.000>
user = 'https://bugs.python.org/scav'

bugs.python.org fields:

activity = <Date 2002-03-25.08:43:52.000>
actor = 'scav'
assignee = 'none'
closed = True
closed_date = None
closer = None
components = ['None']
creation = <Date 2002-03-22.15:43:49.000>
creator = 'scav'
dependencies = []
files = []
hgrepos = []
issue_num = 533632
keywords = []
message_count = 5.0
messages = ['9914', '9915', '9916', '9917', '9918']
nosy_count = 3.0
nosy_names = ['tim.peters', 'loewis', 'scav']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue533632'
versions = []

[scav]

>>> a=1L
>>> type(a)
<type 'long'>
>>> a
Bus error(coredump)

F***! Nearly everything else works. It just seems to
be something in repr() of a long that crashes it.

Anyone else have this problem?

[loewis]

Logged In: YES
user_id=21627

Can you use a debugger to find out and report where it crashes?

[loewis]

Logged In: YES
user_id=21627

Can you please also report which compiler you have been using?

[tim-one]

Logged In: YES
user_id=31435

Peter, no, there have been no other reports of this on 64-
bit platforms. If possible, try recompiling longobject.c
with optimization disabled. Its internal long_format()
routine is complicated so has a better-than-usual chance of
provoking bad code generation.

[scav]

Logged In: YES
user_id=8911

Thanks all.

I am using the HP-UX ANSI C compiler (cc -Ae).

Recompiling longobject.c without optimisations worked OK,
so I'm content.

If no similar problems emerge, I'll not need to learn how
to use the debugger (adb, which I find fairly daunting!)

Peter