From chiark.chu.cam.ac.uk!ijackson Wed May 22 09:23:37 1996
Return-Path: <ijackson@chiark.chu.cam.ac.uk>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0uMGhE-0007hzC; Wed, 22 May 96 09:23 PDT
Received: from artemis.chu.cam.ac.uk by pixar.com with SMTP id AA01363
  (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Wed, 22 May 1996 09:23:35 -0700
Received: from chiark.chu.cam.ac.uk by artemis.chu.cam.ac.uk with smtp
	(Smail3.1.29.1 #33) id m0uMGgv-0007wYC; Wed, 22 May 96 17:23 BST
Received: by chiark.chu.cam.ac.uk
	id m0uMG59-0002bQC
	(Debian /\oo/\ Smail3.1.29.1 #29.35); Wed, 22 May 96 16:44 BST
Message-Id: <m0uMG59-0002bQC@chiark.chu.cam.ac.uk>
Date: Wed, 22 May 96 16:44 BST
From: Ian Jackson <ijackson@chiark.chu.cam.ac.uk>
To: Debian bugs submission address <debian-bugs@pixar.com>
Subject: Perl dumps core

Package: perl
Version: 5.002-7

The bug processing script on master.debian.org causes Perl to dump
core with a SIGSEGV.

I have the coredump, and can supply it and the script and the data it
was processing.  The bug is quite reproducible.

I *need* this bug fixed *within weeks*; I can't move the bug system to
master until this problem is sorted out, and the bug system is
overflowing both my disk and CPU quotas on the system I'm currently
using.  I estimate that I'll have to shut it down halfway through
June, if current resource usage continues.

I'm using the following libraries:
$ ldd /usr/bin/perl
        libgdbm.so.1 => /usr/lib/libgdbm.so.1
        libdb.so.1 => /usr/lib/libdb.so.1
        libdl.so.1 => /lib/libdl.so.1.7.10
        libm.so.5 => /lib/libm.so.5.0.5
        libc.so.5 => /lib/libc.so.5.3.5
$ 

These are mainly Debian ones; the libc.so.5 is home-grown on master,
but I've tried it with Debian's 5.2.18 and LD_LIBRARY_PATH, and that
didn't help.

Ian.

PS: Please note the correct email address when replying.