freebsd stable - Aug 2004 - apache segfault caused by latest c-client.

I'm running 4.10-STABLE and last week ran into an especially frustrating 
segfault in my apache logs when trying to login to Horde+IMP.  An 
example[1] is below.  I tried debugging via gdb, which yields the 
corresponding error:

| Program received signal SIGSEGV, Segmentation fault.
| 0x28609fba in ip_nametoaddr () from /usr/local/lib/libc-client4.so.8

... and then:

| # pkg_which /usr/local/lib/libc-client4.so.8
| cclient-2004,1

It looks like c-client is the culprit.  After this I refined my google 
searches and found others had fixed the problem by switching to an older 
version of c-client.  How can I do this safely without breaking the 
other ports (namely UW IMAP itself) that rely on my current c-client 
installation?

--
Sahil Tandon <sahil@hamla.org>

[1] [notice] child pid 88766 exit signal Segmentation fault (11)

guy@device.dyndns.org wrote:

[...]
> You may use the sysutils/portdowngrade port to achieve this.
Neat.  But how can I "pause" (for lack of a more technically accurate 
term) to manipulate the cclient patches (I need to add 
CREATEPROTO=mbxproto support) before portdowngrade automatically 
launches portupgrade in its final step?

--
Sahil Tandon <sahil@hamla.org>

Hello,

Le Mer  4 ao? 04 ?  3:27:39 +0200, Sahil Tandon <sahil@hamla.org>
 ?crivait?:
> I'm running 4.10-STABLE and last week ran into an especially
frustrating
> segfault in my apache logs when trying to login to Horde+IMP.  An 
> example[1] is below.  I tried debugging via gdb, which yields the 
> corresponding error:
> 
> | Program received signal SIGSEGV, Segmentation fault.
> | 0x28609fba in ip_nametoaddr () from /usr/local/lib/libc-client4.so.8
> 
> ... and then:
> 
> | # pkg_which /usr/local/lib/libc-client4.so.8
> | cclient-2004,1
> 
> It looks like c-client is the culprit.  After this I refined my google 
> searches and found others had fixed the problem by switching to an older 
> version of c-client.  How can I do this safely without breaking the 
> other ports (namely UW IMAP itself) that rely on my current c-client 
> installation?
A new release of cclient has been released. The changelog says
"imap-2004a is a maintenance release, consisting primarily of critical
bugfixes."

Could you please upgrade to this release (apply the following patch),
rebuild your php4-imap-4.3.8_2, and check if it fixes your errors?

--- cclient.diff begins here ---
diff -urN mail/cclient.orig/Makefile mail/cclient/Makefile
--- mail/cclient.orig/Makefile  Fri Jun  4 16:21:47 2004
+++ mail/cclient/Makefile       Fri Aug  6 21:51:03 2004
@@ -6,7 +6,7 @@
 #
 
 PORTNAME=      cclient
-PORTVERSION=   2004
+PORTVERSION=   2004a
 PORTEPOCH=     1
 CATEGORIES=    mail devel ipv6
 MASTER_SITES=  ftp://ftp.cac.washington.edu/imap/%SUBDIR%/ \
diff -urN mail/cclient.orig/distinfo mail/cclient/distinfo
--- mail/cclient.orig/distinfo  Fri Jun  4 16:21:47 2004
+++ mail/cclient/distinfo       Fri Aug  6 21:51:46 2004
@@ -1,2 +1,2 @@
-MD5 (imap-2004.tar.Z) = ec3dafeeae320457a1d098157e9bf969
-SIZE (imap-2004.tar.Z) = 2220333
+MD5 (imap-2004a.tar.Z) = 34d2c66271302cd2f926094fb5e8705d
+SIZE (imap-2004a.tar.Z) = 2224181
--- cclient.diff ends here ---

Regards,
-- 
Th. Thomas.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url :
http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20040806/ce47eb71/attachment.bin