Re: Maildrop 1.4.0 problems on sparc

[Michael Coulter <mjc@raistlin.bitz.ca>]

Just to check if gcc's optimization was at fault, I added -O0
to the COPTS in /etc/mk.conf and recompiled maildrop. Still no luck.
One thing that does confuse me though is that maildrop is dying in
a call to abort

Program received signal SIGABRT, Aborted.
0x852c1c8 in abort ()
(gdb) bt
#0  0x852c1c8 in abort ()
#1  0x8264af3 in __rethrow (index=0x1)
#2  0x8264b1b in __terminate ()
#3  0x826560f in __throw ()
#4  0x19e3f in ?? ()
#5  0x2f95b in ?? ()
#6  0x1a713 in ?? ()
#7  0x113bb in ?? ()


however, I don't see any abort() calls in maildrop's source ?