On Thu, 13 Jul 2006, Jaime wrote:
No, and the issue is on an in-production server with lots of
inter-dependent software. So I'm *very* hesitant to do as you suggest. I'd
be willing to do that on a test server (e.g. the old server that the data
was moved off of). The problem is that this is the only box with these
symptoms.
So the problem only happens on the new box?
One thing that may work for you: you could try installing the unmodified
UW imapd on a different port other than 143, and then configure a test
version of PHP to use that port.
By any chance, did you compile the software in 64-bit mode? If so, try
compiling it in 32-bit mode. I have heard of some issues with 64-bit
compiles; and the software currently doesn't try to work in other than
32-bit mode.
I tried to make it portable for other byte sizes; and it does port to
16-bit (and 36-bit!!) systems. Unfortunately, the people who decided
matters for 64-bits made different choices than I expected when I wrote
the code. For example, they decided upon "long long" for 64-bit values; I
expected in 1988 that they would keep the K&R short/int/trichotomy when
64-bit time rolled along. Silly me.
FWIW, I'm using the code from FreeBSD 6.1's ports collection as of
Tuesday. I cvsup'd the code that afternoon.
Unfortunately, I have nothing to do with (much less any control over) the
FreeBSD (or other third-party) distribution. I don't even try to keep
track of what any of these guys do.
Other than the 64-bit issue mentioned above, I am not aware of any SEGV
bugs in the UW distributions of either imap-2004g (the release version) or
imap-2006 (the development version). As soon as I become aware of any
SEGV bug, I fix it and update the UW distribution.
One other possibility that came to mind is that a common third-party patch
makes the c-client library be a shared library, instead of a static part
of the program binary. This really doesn't save all that much on modern
systems (even with static linking, multiple instances of the same program
share their code pages). More to the point, I've seen cases where the
shared library of c-client was for some other version than what the
application was built to use, and the resulting version skew resulted in
crashes.
So, if c-client is a shared library, try it with a static link. If the
problem vanishes, so much the better...
Can you explain how to make a trace log?
That's a function of the client application. I could tell you how to do
it in Pine but not in most other applications and definitely not in PHP.
I hate to give you an "RTFM", but in the case of PHP I really don't know
the answer and would have to RTFM myself..... :-)
Thanks for the reply. In several days of trying every resource that
I could think of (FreeBSD mailing list, Usenet, Web, local Linux group,
etc.) this was the most productive response that I've had.
Thanks. I hope that some of the above is useful. Good luck, and please
let me know how it goes.
-- Mark --
http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.
_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
