squat core dump

[Henrique de Moraes Holschuh]

On Wed, 08 Jan 2003, Ilya wrote:
> Today one of my users complained that the inbox doesnt show any messages.
> Upon investigation I saw that messages are still present, however there was an
> imapd.core file in that user's dir
> any suggestions?
> this is gdb trace:
> #0  0x8076036 in memconst (s=0x2849cff2 <Address 0x2849cff2 out of bounds>,
> len=16, v=0) at squat.c:80
> 80      squat.c: No such file or directory.
> (gdb) where
> #0  0x8076036 in memconst (s=0x2849cff2 <Address 0x2849cff2 out of bounds>,
> len=16, v=0) at squat.c:80
> #1  0x807624a in squat_search_open (fd=14) at squat.c:133
> #2  0x8075e2f in search_squat (msg_list=0x8127c00, mailbox=0x810b180,
> searchargs=0x812c180) at search_engines.c:257

Squat does some really scary (and forbidden) things, which are NOT fixable
without some code rewrite, at least not in a portable way.  See the bugzilla
for Cyrus, I have a bug open there about it.

BTW, it is possible to fix it in Linux, and I guess it can also be done in
Solaris (both being sensible enough in their mmap implementations).  But not
in all platforms.

Now, as a workaround, kill all squat files that are giving you trouble, and
reindex that mailbox...  If you're lucky, that will fix it.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh