SIGABRT is not handled explicitely by the code. No handler is
installed. This could be os-specific. What are
you running on?
FreeBSD 5.3 Stable, dbmail_2_0_branch cvs checkout a few days
before the 2.0.1 release. Sidenote: I replaced the default
dbmail CFLAGS "-g -O2" with "-O -pipe", but didn't think this
would result in a SIGABRT?
Nope, it's not.
I've never seen a kernel logline like your's
with the kernel-path specified. But all I know is
linux...
That's from a custom patch I applied to FreeBSD's msyslog port
to get it running on FreeBSD 5.
But what confuses me even more now, is that this signal even
occurs upon QUIT in a pop3 session. Is this the case on Linux,
too?
Heh, my logs are *filled* with crashed dbmail backends at the moment.
In the last week, things have gotten worse in that regard, though I
haven't had the time to figure out why. -sc
--
Sean Chittenden
