Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!apple!amdahl!JUTS!kpc00
From: kpc00@JUTS.ccc.amdahl.com (kpc)
Newsgroups: comp.lang.perl
Subject: Re: possible patchlevel 37 bug (memory leak?)
Message-ID: <KPC00.90Oct30184121@JUTS.ccc.amdahl.com>
Date: 31 Oct 90 02:41:21 GMT
References: <COMPOSER.90Oct24220939@chem.bu.edu>
	<10108@jpl-devvax.JPL.NASA.GOV> <1195@digi.lonestar.org>
	<10163@jpl-devvax.JPL.NASA.GOV>
Sender: kpc00@ccc.amdahl.com
Organization: my-organization
Lines: 19
In-reply-to: lwall@jpl-devvax.JPL.NASA.GOV's message of 30 Oct 90 00:54:34 GMT


Did nobody outside of this site get my "1 2 3" post here?  (About a2p,
speed, scheme, etc?)

In article <10163@jpl-devvax.JPL.NASA.GOV>
lwall@jpl-devvax.JPL.NASA.GOV (Larry Wall) writes:

   In article <1195@digi.lonestar.org> kgallagh@digi.lonestar.org (Kevin Gallagher) writes:
   : Several people here use the perl debugger quite a lot.  We all got bit by this
   : $0 problem causing a "segmentation fault".  Rather than back out pl 37, I

What are the symptoms of the bug?  My a2p output crashes the debugger.

Thanks.
--
If you do not receive a reply from me, please resend your mail;
occasionally this site's mail gets delayed.

Neither representing any company nor, necessarily, myself.