amd64/182843: application crashes when compiled with clang 3.3

[Alex]

>Number:         182843
>Category:       amd64
>Synopsis:       application crashes when compiled with clang 3.3
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-amd64
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Oct 09 00:00:00 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator:     Alex
>Release:        9.2-RELEASE (amd64)
>Organization:
>Environment:
FreeBSD srv.mydomain.net 9.2-RELEASE FreeBSD 9.2-RELEASE #2 r255961: Tue Oct  1 16:37:11 EST 2013     root at srv.mydomain.net:/usr/obj/usr/src/sys/custom_xen  amd64
>Description:
Hi Guys,

Posted this to the freebsd-general mailing list. As I have heard nothing, I thought it would be appropriate to file a PR.

There seems to be an issue that has cropped up since upgrading from 9.1-RELEASE (amd64) to 9.2-RELEASE (amd64)), in that a port (net-im/jabber) crashes frequently with signal 10 errors frequently (bus error) when built with the version of Clang shipped in 9.2-RELEASE.

-----------
pid 1880 (jabberd14), uid 93: exited on signal 10
pid 8368 (jabberd14), uid 93: exited on signal 10
pid 8586 (jabberd14), uid 93: exited on signal 10
pid 9100 (jabberd14), uid 93: exited on signal 10
pid 9198 (jabberd14), uid 93: exited on signal 10
pid 9314 (jabberd14), uid 93: exited on signal 10
pid 24565 (jabberd14), uid 93: exited on signal 10
----------

I have recompiled this port without Clang (using the base gcc compiler) and it has not crashed once since (sig 10 bus error crashes are gone). Funnily enough, in FreeBSD 9.1-RELEASE, the same port compiled with Clang 3.1 did not crash ever. So it is a reasonable assumption that the issue has to be related to Clang 3.3.

I have the following in my /etc/make.conf (for clang building):

root at srv:~ # cat /etc/make.conf
NO_PROFILE=true
CC=clang
CXX=clang++
CPP=clang-cpp

Whilst building the port with the base compiler is a workaround, it's not a long term solution, since Clang will be the default Compiler in the not so distant future.

It appears there is no maintainer for this port?

Software= jabber-1.6.1.1_13,1
MAINTAINER=     ports at FreeBSD.org
COMMENT=        XMPP/Jabber server daemon

I assume the above email is just a generic email address for ports who do not have a maintainer? I suspect the issue to be compiler specific.

>How-To-Repeat:
Build the net-im/jabber port using clang. I have the following options enabled for the port 'config':

* ipv6
* MySQL

So some basic configuration so that the software will run.

Crashes can be observed anywhere from 5-10 minutes after starting the software or maybe even 2 hours later. There is no specific event in any log that seems to lead to the crash, it appears to be entirely random.

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted: