Path: utzoo!utgpu!watserv1!watmath!att!att!emory!wuarchive!zaphod.mps.ohio-state.edu!ncar!elroy.jpl.nasa.gov!jpl-devvax!lwall From: lwall@jpl-devvax.JPL.NASA.GOV (Larry Wall) Newsgroups: comp.lang.perl Subject: Re: possible patchlevel 37 bug (memory leak?) Message-ID: <10163@jpl-devvax.JPL.NASA.GOV> Date: 30 Oct 90 00:54:34 GMT References: <10108@jpl-devvax.JPL.NASA.GOV> <1195@digi.lonestar.org> Reply-To: lwall@jpl-devvax.JPL.NASA.GOV (Larry Wall) Organization: Jet Propulsion Laboratory, Pasadena, CA Lines: 21 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 : thought it should be easy to fix perly.c myself, encouraged by your comment : above. Well, I tried and failed. Your comment suggested to me that the : following change should be made: : : From: magicalize("!#?^~=-%0123456789.+&*()<>,\\/[|`':\024"); : To: magicalize("!#?^~=-%123456789.+&*()<>,\\/[|`':\024"); : : which just deletes "0" from the list. It did not work. Am I missing : something obvious? You also have to say 713c713 < str_set(STAB_STR(tmpstab),origfilename); --- > str_set(stab_val(tmpstab),origfilename); Larry