On Wed, Aug 19, 1998 at 07:30:55AM +0100, Jeffrey Goldberg wrote:
> On Tue, 18 Aug 1998, Michael Hall wrote:
>
> > For being just some innocuous code it doesn't like something, as you
> > can see it bombs out on 's/^\s*//g;' and never gets to print 'ok 3'.
> > Makes no sense to me, maybe I don't know as much as I thought I did about
> > perl :-)
>
> There has been some discussion of that on this list. It appears that that
> bizarre regex leads perl 5.005 to a segmentation violation. You're right
> to not understand that substitution: perl doesn't understand it either.
> You can safely remove the 'g' suffix and all will be well.
>
> The perl developers have been informed.
I'm using 5.004_4. I went ahead and removed the 'g' from the two lines
I had commented out:
s/^\s*//; # strip leading whitespace
s/\s*$//; # strip trailing whitespace
and it now runs (to an extent). I can do 'lists', 'help' but thats about
it. 'config <list> <list>.admin', 'subscribe <list>' all bomb with the
same 'unknown mailer error 22' and nothing logged anywhere in more detail,
no 'core' files either. Tried looking through the files for more
occurences of 's/whatever/whatever/g' and found quite a few but I didn't
know which ones would be safe to remove as they looked legitimate since
the pattern could appear multiple times, not like the above two lines
where the pattern could appear only once.
Any other thoughts ? Maybe its my perl setup or is it just a plain
old perl problem ? What other things/places could/should be edited ?
I've been dead before. - Captain Spock, Star Trek VI
--
Mike Hall <mhall@riverside.org> - On the net at http://www.riverside.org
System Administrator (*nix, Perl, CGI hacker, certified OS/2 Specialist)
Follow-Ups:
References:
|
|
