Bug 6611 - Test Suite Failure: t/db_awl_perms.t Segmentation fault with shell script.
Summary: Test Suite Failure: t/db_awl_perms.t Segmentation fault with shell script.
Status: RESOLVED WONTFIX
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Building & Packaging (show other bugs)
Version: 3.3.2
Hardware: PC Linux
: P2 normal
Target Milestone: 3.3.2
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-31 18:51 UTC by D. Stussy
Modified: 2011-08-11 20:00 UTC (History)
1 user (show)


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description D. Stussy 2011-05-31 18:51:50 UTC 
SA 3.3.2-rc2:

t/db_awl_perms.t .................. sh: line 1:  7162 Segmentation fault      
/usr/bin/perl -T -w ../spamassassin.raw -C log/test_rules_copy --siteconfigpath log/localrules.tmp -p log/tst.cf --add-addr-to-whitelist whitelist_test@example.org > log/d.db_awl_perms/1

System:  Linux 2.6.39 (from source) under Slackware 64-bit 13.1
Hardwr:  6-core AMD Opertron 2.8GHz, 32GB ram
Shell:   Bash 4.1.007  and  Perl 5.14.0
Comment 1 Mark Martinec 2011-06-03 14:34:58 UTC 
> SA 3.3.2-rc2:
> t/db_awl_perms.t .................. sh: line 1:  7162 Segmentation fault      
> /usr/bin/perl -T -w ../spamassassin.raw -C log/test_rules_copy --siteconfigpath
> log/localrules.tmp -p log/tst.cf --add-addr-to-whitelist
> whitelist_test@example.org > log/d.db_awl_perms/1
> 
> System:  Linux 2.6.39 (from source) under Slackware 64-bit 13.1
> Hardwr:  6-core AMD Opertron 2.8GHz, 32GB ram
> Shell:   Bash 4.1.007  and  Perl 5.14.0

My suspect is that a perl module to access a database (the BerkeleyDB
module presumably) was not reinstalled when perl was upgraded.
Comment 2 D. Stussy 2011-06-03 19:01:01 UTC 
Perhaps, but I used the perl configuration option to search prior versions' installation (and BDB was installed as part of 5.12.3).
Comment 3 D. Stussy 2011-08-11 20:00:03 UTC 
The problem has not re-occurred when I upgraded to the official 3.3.2 release.
Closing as wontfix (could also be invalid).