segmentation fault in test_re

[hoel]

BPO	870120

^{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 2004-05-16.15:30:03.000>
created_at = <Date 2004-01-03.22:44:59.000>
labels = []
title = 'segmentation fault in test_re'
updated_at = <Date 2004-05-16.15:30:03.000>
user = 'https://bugs.python.org/hoel'

bugs.python.org fields:

activity = <Date 2004-05-16.15:30:03.000>
actor = 'hoel'
assignee = 'none'
closed = True
closed_date = None
closer = None
components = ['None']
creation = <Date 2004-01-03.22:44:59.000>
creator = 'hoel'
dependencies = []
files = []
hgrepos = []
issue_num = 870120
keywords = []
message_count = 2.0
messages = ['19526', '19527']
nosy_count = 1.0
nosy_names = ['hoel']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue870120'
versions = []

[hoel]

I'm building python 2.3.3 on a SuSE Linux 9.0 with
kernel 2.4.21-144-athlon using "gcc (GCC) 3.3.1 (SuSE
Linux)". When using

./configure --with-thread --with-fpectl
--with-signal-module \
--with-pymalloc --enable-shared --with-cxx=g++

make test

I get

....
test_quopri
test_random
test_re
make: *** [test] Segmentation fault

Leaving out the "--enable-shared" switch testing
succeeds. After some conversation on comp.lang.python i
fiddeled with USE_RECURSION_LIMIT in Modules/_sre.c.
Setting it to a value of 6835 testing succeeds with
"--enable-shared". Setting it 6840 I get the
segmentation fault.

[hoel]

Logged In: YES
user_id=81913

Tis is fixed in CVS, but bug persists in 2.3.4c1