Path: utzoo!utgpu!watserv1!watmath!att!att!emory!samsung!cs.utexas.edu!sun-barr!newstop!west!texsun!digi.lonestar.org!kgallagh From: kgallagh@digi.lonestar.org (Kevin Gallagher) Newsgroups: comp.lang.perl Subject: Re: possible patchlevel 37 bug (memory leak?) Message-ID: <1195@digi.lonestar.org> Date: 29 Oct 90 18:17:49 GMT References: <10108@jpl-devvax.JPL.NASA.GOV> Organization: DSC Communications, Plano Tx. Lines: 25 In article <10108@jpl-devvax.JPL.NASA.GOV> lwall@jpl-devvax.JPL.NASA.GOV (Larry Wall) writes: >In article composer@chem.bu.edu writes: >No, it turns out to be simply that $0 was still being treated as a magical >variable in one spot but not in another. >[stuff deleted] > >The trivial fix is to not mark $0 as magical in perly.c. >>patch38 > 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? -- ---------------------------------------------------------------------------- Kevin Gallagher kgallagh@digi.lonestar.org OR ...!uunet!digi!kgallagh DSC Communications OR apcihq!apcidfw!digi!kgallagh ----------------------------------------------------------------------------