Re: segmentation fault on HTML::TokeParser

I think I was getting segfaults with the same family on OS X about 5 years ago. Never tracked it down but if it was a problem it'll be in old tests/lists (check by perl version?). Just curious, sounds like you're doing exactly what HTML::Truncate does so maybe give it a whirl and see if the problem persists. If it goes away it might be because your code has a weird recursion or something that your laptop can handle but the shared host can't.

I also use DreamHost for some things and when they refused to upgrade their WWW::Mechanize when it would not even compile, I started keeping my own Perl local lib for everything. No problems since. You should open a cpan shell, run 'r' and use the list as a guide to upgrade everything that's relevant; not just the parser.

Comment on Re: segmentation fault on HTML::TokeParser

Replies are listed 'Best First'.
Re^2: segmentation fault on HTML::TokeParser by punkish (Priest) on Mar 28, 2008 at 16:20 UTC
Good grief! HTML::Truncate indeed claims to do what I am trying to reinvent. I will give it a whirl, and hopefully it won't crash and burn. Update: Yes, HTML::Truncate works on Dreamhost without segfaulting. Problem solved for now. Many thanks. Wrt Dreamhost, yes, I do have my own lib, and that is where I installed HTML::TokeParser (after finding their version very old). Nevertheless, segfaults abound. -- when small people start casting long shadows, it is time to go to bed	[reply]

Replies are listed 'Best First'.

Re^2: segmentation fault on HTML::TokeParser
by punkish (Priest) on Mar 28, 2008 at 16:20 UTC

Update: Yes, HTML::Truncate works on Dreamhost without segfaulting. Problem solved for now.

Many thanks. Wrt Dreamhost, yes, I do have my own lib, and that is where I installed HTML::TokeParser (after finding their version very old). Nevertheless, segfaults abound.

--

when small people start casting long shadows, it is time to go to bed

[reply]