On Thu, 20 Jun 2002, Joerg Sommer wrote:
> my exim (debian 3.35-1) crashes with signal 11 since I set the flag
> queue_only=true.
I don't know what Debian did to Exim to make their version. Certainly
lots of people use queue_only=true.
> I checked my RAM, but there is nothing. I compiled the
> debian package new with debugging symbols and the error never occured
> since then.
Oh dear. That kind of bug is always nasty.
> 17721 strchr("hlL", 's') = NULL
> 17721 sprintf("alea.gnuu.de", "%*.*s", 12, 12, "alea.gnuu.de") = 12
> 17721 strcpy(0x080c3ad8, "T:|/usr/lib/news/bin/mailpost -a"...) = 0x080c3ad8
> 17721 _setjmp(0x080ba880, 0x080c96d0, 0x080c96a8, 0x40000000, 0x080c38d8) = 0
> 17721 signal(11, 0x08050e10 <unfinished ...>
> 17721 SYS_rt_sigaction(11, 0xbfffeeb4, 0xbfffee28, 8, 11) = 0
> 17721 <... signal resumed> ) = NULL
> #v-
>
> So is it possible, that there is a bug?
It's *always* possible there is a bug. Usually more than one. :-)
The only use of setjmp() within Exim 3 is when it is trying to catch
errors opening DBM files. This dates back to early days when the locking
was done differently. In Exim 4, there are no instances of setjmp.
This looks like a crash inside a DBM library. These are usually caused
by mismatches between different library versions. Maybe re-compiling has
sorted out the problem. (Might as well be optimistic.)
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
