OSF/1 test_dbm segfaults

[anthonybaxter]

BPO	814996

^{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 2008-01-28.22:01:21.782>
created_at = <Date 2003-09-30.09:53:35.000>
labels = []
title = 'OSF/1 test_dbm segfaults'
updated_at = <Date 2008-01-28.22:01:21.775>
user = 'https://bugs.python.org/anthonybaxter'

bugs.python.org fields:

activity = <Date 2008-01-28.22:01:21.775>
actor = 'draghuram'
assignee = 'none'
closed = True
closed_date = <Date 2008-01-28.22:01:21.782>
closer = 'draghuram'
components = ['None']
creation = <Date 2003-09-30.09:53:35.000>
creator = 'anthonybaxter'
dependencies = []
files = []
hgrepos = []
issue_num = 814996
keywords = []
message_count = 3.0
messages = ['60403', '60404', '61802']
nosy_count = 2.0
nosy_names = ['anthonybaxter', 'draghuram']
pr_nums = []
priority = 'normal'
resolution = 'out of date'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue814996'
versions = []

[anthonybaxter]

When running regrtest on OSF/1 5.1, I get a segfault in
test_dbm. Running test_dbm alone works. I'll try and
nail down the sequence that causes the crash.

[anthonybaxter]

Logged In: YES
user_id=29957

a short update: this appears to be something bogus with the
OSF/1 dynamic object support with -ldbm. Don't think it's
fixable in a sane way for 2.3.2

[draghuram]

I am assuming that this can be closed considering that there is no
activity for a long time.