[Mimedefang] mimedefang-multiplexor slave segfaults
whit at transpect.com
Fri Oct 26 10:56:11 EDT 2007
Looks like there may be other problems in how my system's set up, in regards
to diagnosing this:
# gdb /usr/local/bin/mimedefang-multiplexor 15123
GNU gdb 6.6
Using host libthread_db library "/lib/libthread_db.so.1".
Attaching to program: /usr/local/bin/mimedefang-multiplexor, process 15123
(no debugging symbols found)
Failed to read a valid object file image from memory.
0xb7f93410 in ?? () from /lib/ld-linux.so.2
Program received signal SIGSEGV, Segmentation fault.
0xb7d19f7d in ?? ()
#0 0xb7d19f7d in ?? ()
Cannot access memory at address 0xbf867c30
I'm not even familiar with embedded Perl.
On Fri, Oct 26, 2007 at 10:09:07AM -0400, David F. Skoll wrote:
> Whit Blauvelt wrote:
> > Did as you've suggested, but no core file is showing up in
> > /var/spool/MIMEDefang - or anywhere else on the system. Yet repeatedly:
> > slave 1 (pid 14500) exited due to signal 11 (SLAVE DIED UNEXPECTEDLY)
> That's annoying. About the only thing I can suggest is:
> 1) Run "md-mx-ctrl slaves" to get some slave process IDs
> 2) Attach gdb to one of them:
> gdb /path/to/mimedefang-multiplexor pid_of_slave
> 3) In gdb, type "cont" to let the slave keep running
> 4) Hope that that's the one that dies. If it does, gdb will print a
> message and you can type "where" to get a stack trace.
> Are you using embedded Perl? Try turning that off to see if it
> fixes the problem.
> > Might the slave be effectively started from some other location by the
> > multiplexor, which would need to be made writable for it?
> No; the slaves do a "cd /var/spool/MIMEDefang" as part of their
> NOTE: If there is a disclaimer or other legal boilerplate in the above
> message, it is NULL AND VOID. You may ignore it.
> Visit http://www.mimedefang.org and http://www.roaringpenguin.com
> MIMEDefang mailing list MIMEDefang at lists.roaringpenguin.com
More information about the MIMEDefang