Jeremy Howard wrote:
>
> Ken Murchison wrote:
>
> >I'm running a config almost the same as you and have never seen this
> >problem. AFAIK, the CMU guys have never seen this either. Do you have
> >a core that you can run a backtrace on, or can you force a core by
> >setting MALLOC_CHECK_=2 before starting master (see malloc(3) for
> >details)?
> >
> Most of the segfaults were due to the problem that imapd_out or imapd_in
> were corrupted. The workaround discussed in our patch has solved most of
> these. I'll try and get a core file for the rare segfaults that we still
> get to see what the unresolved issues are. The imapd_out corruption
> problem can't be solved by studying the core file AFAICT because we
> can't see where the corruption is occuring.
If you set MALLOC_CHECK_=2, then imapd will abort() whenever it thinks
that there might be a corruption. By examining this core, it is easier
to track down these problems. I've done this a few times to track down
the subtle errors that have baffled others.
Ken
--
Kenneth Murchison Oceana Matrix Ltd.
Software Engineer 21 Princeton Place
716-662-8973 x26 Orchard Park, NY 14127
--PGP Public Key-- http://www.oceana.com/~ken/ksm.pgp
