Bug 4645 - spamassassin core dump with snoopy
Summary: spamassassin core dump with snoopy
Status: RESOLVED INVALID
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamassassin (show other bugs)
Version: 3.1.0
Hardware: Other Linux
: P1 critical
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords: triage
Depends on:
Blocks:
 
Reported: 2005-10-24 14:53 UTC by Ken Bass
Modified: 2006-12-05 11:31 UTC (History)
0 users


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 Ken Bass 2005-10-24 14:53:25 UTC 
I installed snoopylogger (http://sourceforge.net/projects/snoopylogger/).
snoopylogger hooks into the system via the LD_PRELOAD mechanism. It puts a
wrapper around the 'execv' and 'execve' calls to add logging. 

To reproduce this download snoopylogger and build it. I do not think you need to
install it. Simply run
export LD_PRELOAD=/path/snoopy.so
spamassassin
unset LD_PRELOAD 

You will get a segmentation fault. I noticed this because after I installed
snoopy logger my home directory was full of core files. (no debug symbols so
they were not useful).
Comment 1 Bob Menschel 2005-10-28 08:19:03 UTC 
Normally one doesn't run spamassassin with no parameters and no input. Can you try
export LD_PRELOAD=/path/snoopy.so
spamassassin <MailMessageFile
unset LD_PRELOAD 
and see if the problem still exists? 

Q: Why do you flag this as a critical SA item, if SA does not fail on its own,
but only if you insist on using snoopylogger? I would think you would at least
open a snoopylogger bug so it would be worked on from that end also, no? 

Also, reading
http://sourceforge.net/tracker/index.php?func=detail&aid=612504&group_id=9226&atid=109226
suggests that this may very well be a problem within snoopylogger, since the
symptom (segmentation failure) seems the same. 

Please clarify.
Comment 2 Ken Bass 2005-10-28 16:27:14 UTC 
(In reply to comment #1)
> Normally one doesn't run spamassassin with no parameters and no input. Can you try
 That is true. I was just providing the simplest cast that failed. Each incoming
msg caused a core file in my home directory meaning each procmail invocation of
spamassassin crashed.

> Q: Why do you flag this as a critical SA item, if SA does not fail on its own,
> but only if you insist on using snoopylogger? I would think you would at least
> open a snoopylogger bug so it would be worked on from that end also, no? 

 You have a valid point. I flagged SA because no other application I am running
has shown a problem. It seems specific to SA / snoopylogger interaction and it
causes the filesystem to fill up with core files.

> Also, reading
>
http://sourceforge.net/tracker/index.php?func=detail&aid=612504&group_id=9226&atid=109226
> suggests that this may very well be a problem within snoopylogger, since the
> symptom (segmentation failure) seems the same. 

 Thank you for pointing this out. I will examine the snoopylogger code in detail
and see if I can fix that myself. Perhaps the segfault is within a subsequent
exec call with corrupted argument sizes.
Comment 3 Theo Van Dinter 2006-12-05 11:31:51 UTC 
This isn't a SpamAssassin issue as far as I can see.  It's either an issue with
snoopy or perl.