Hi, On Fri, 6 Jun 2003 12:59:05 -0700 [EMAIL PROTECTED] (Lydia Leong) wrote:
> I'm installing SpamAssassin for the first time in the following > environment: > > - Irix 6.5 > - perl 5.6.1 (from the SGI freeware site, with a modified Config.pm > to make the compile defaults gcc instead of SGI cc) Ha! So it's not just Sun that breaks perl by compiling it with a compiler that doesn't ship by default! :) Seriously though, this makes two instances of changing Config.pm to work around a vendor's missing compiler. Do you have instructions for fixing Config.pm on IRIX? I documented Solaris 2.6 and 7 and the fix for 8 and 9 are similar. Any HP-UX or AIX users with the same problems & solutions? A comprehensive "fixing your vendor's broken perl installation" document would come in handy for more than just SA. > - New, clean, installs of HTML::Parser, etc. > - gcc 2.95.2 > > It builds cleanly. > > However, when I go to run the spamassassin test on the two sample > pieces of email, there is no output; instead, there is a brief hang > followed by a core dump (of perl). > > If I start spamd before I run spamassassin, it, too, will dump core. > > For that matter, simplier invocations will cause perl to dump core: > spamassassin --help and spamd --help both die on segmentation violations, > too. Q: Assuming IRIX has some equivalent to truss or strace (system call trace utility), can you tell what's prompting the core dump? Is SA the only code that exhibits this behavior? My gut feeling is the problem lies with perl not SA; a bad script shouldn't cause a core dump. -- Bob Apthorpe ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
