Re: [Mutt] #2958: mutt-1.5.16: mutt crash at start when enabling
#2958: mutt-1.5.16: mutt crash at start when enabling header caching in nsf
directory with a (non-root) install
Comment (by Jiang Qian):
{{{
On Mon, Sep 17, 2007 at 08:55:21AM -0000, Mutt wrote:
> #2958: mutt-1.5.16: mutt crash at start when enabling header caching in
nsf
> directory with a (non-root) install
>
> Comment (by pdmef):
>
> Replying to [comment:2 Jiang Qian]:
> > > Comment (by pdmef):
>
> > > Is there any chance this is related to MD5 and is fixed by
changeset
> > > [c699e5847630]? What types are both machines (little or big
endian)?
>
> > I'm no computer science major. So how do I find out the endianness of
> > the machines? The former is a debian 3.1 on a Xeon machine. The
latter
> > is a ubuntu 5.04 on a pentium M machine. Let me know what further
> > debugging I can do.
>
> It's not endian related as Xeon and Pentium M are little endian.
>
> Now I re-read your report. I have a couple more questions:
>
> Does "mbox" really mean the mbox format? If yes: header caching for
mbox
> folders is not implemented as it doesn't make sense. Hence mutt can't
> crash for mbox because of header caching.
My mistake. What crashes mutt is the imap mailbox.
>
> Also, are you using the very same header cache on both systems via NFS?
If
> yes, then please don't do as 1) pentium M is 32bit and Xeon is 64bit.
This
> begs for trouble.
No, I deleted the whole header cache folder and started anew, it still
crash mutt. My local machine that works fine does not use NFS. The
header cache are stored in local hard drive. Also, the Xeon in the
remote server is in fact a very old Xeon, which is 32 bit, I believe.
>
> Can you please find out with what database library you've compiled mutt
> with (run 'ldd `which mutt´')?
For remote machine(on which mutt crashes):
libncursesw.so.5 => /usr/lib/libncursesw.so.5 (0x4002a000)
libssl.so.0.9.7 => /usr/lib/i686/cmov/libssl.so.0.9.7
(0x40070000)
libcrypto.so.0.9.7 => /usr/lib/i686/cmov/libcrypto.so.0.9.7
(0x400a1000) libdb-4.3.so => /usr/lib/libdb-4.3.so (0x401a0000)
libc.so.6 => /lib/libc.so.6 (0x40285000)
libdl.so.2 => /lib/libdl.so.2 (0x403b8000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
For local machine(where mutt is fine):
libncursesw.so.5 => /usr/lib/libncursesw.so.5 (0xa7f5e000)
libssl.so.0.9.7 => /usr/lib/i686/cmov/libssl.so.0.9.7
(0xa7f2f000)
libcrypto.so.0.9.7 => /usr/lib/i686/cmov/libcrypto.so.0.9.7
(0xa7e38000) libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0xa7e22000)
libdb-4.2.so => /usr/lib/libdb-4.2.so (0xa7d4c000)
libc.so.6 => /lib/tls/i686/cmov/libc.so.6 (0xa7c1f000)
libdl.so.2 => /lib/tls/i686/cmov/libdl.so.2 (0xa7c1c000)
libresolv.so.2 => /lib/tls/i686/cmov/libresolv.so.2 (0xa7c0b000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0xa7fb8000)
Jiang
>
> --
> Ticket URL: <http://dev.mutt.org/trac/ticket/2958#comment:3>
>
}}}
--
Ticket URL: <http://dev.mutt.org/trac/ticket/2958#comment:>