Hello,
I got access and it is actually gcc, here are the compile options:
$ gmake Q=0 Makefile.defs defs skipped gcc -g -O9 -funroll-loops -m64 -mcpu=ultrasparc -mtune=ultrasparc -fno-strict-overflow -ftree-vectorize -Wall -DNAME='"kamailio"' -DVERSION='"3.3.0-pre3"' -DARCH='"sparc64"' -DOS='solaris_' -DOS_QUOTED='"solaris"' -DCOMPILER='"gcc 4.6.2"' -D__CPU_sparc64 -D__OS_solaris -DSER_VER=3003000 -DCFG_DIR='"/usr/local/etc/kamailio/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DDNS_IP_HACK -DUSE_IPV6 -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DUSE_DNS_CACHE -DUSE_DNS_FAILOVER -DUSE_DST_BLACKLIST -DUSE_NAPTR -DWITH_XAVP -DF_MALLOC -DMEM_JOIN_FREE -DUSE_TLS -DTLS_HOOKS -DUSE_CORE_STATS -DSTATISTICS -DMALLOC_STATS -DWITH_AS_SUPPORT -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DCC_GCC_LIKE_ASM -DSPARC64_MODE -DHAVE_GETIPNODEBYNAME -DHAVE_SYS_SOCKIO_H -DHAVE_SCHED_YIELD -DHAVE_ALLOCA_H -DUSE_SIGACTION -DHAVE_DEVPOLL -DHAVE_SELECT -DHAVE_FILIO_H -DMODS_DIR='"/usr/local/lib64/kamailio/modules:/usr/local/lib64/kamailio/modules_s:/usr/local/lib64/kamailio/modules_k"' -c main.c -o main.o -MMD -MP
I am doing some tests right now to see if I catch soemthing.
Cheers, Daniel
On 6/11/12 10:21 AM, Jason Penton wrote:
This seems like a really strange bug, what compiler are you using, gcc or sun studio? We use gcc and don't have any issues like this. I will use sun studio if you confirm that you are using it and will give that a go.
Cheers Jason
On Mon, Jun 4, 2012 at 8:57 AM, Daniel-Constantin Mierla <miconda@gmail.com mailto:miconda@gmail.com> wrote:
Hello, still strange with the crash on that if condition. One of your previous reports showed a different line, when assigning a pointer. Also, I kind of understood that save() was ok, but lookup() not. Is not the case anymore as the backtrace shows. SIGBUS can occur because of alignment in memory which is thrown in solaris, does not happen in linux flavours. I am thinking of putting the prefix field first so the access to it is at beginning of the straucture, just to see if that is the problem, although is should not be. I will add a patch soon, otherwise I am out of ideas for the moment with the SIGBUS, I would need access to the machine to do some testing by myself. Cheers, Daniel On 6/2/12 10:36 PM, Akan wrote:
Ok, I reloaded the servers with v3.2 from git without performing the checkout and with just the master branch. Reran my tests on 2 servers and Kamailio terminated with a core dump. I have included the full trace of one of the servers. The other trace has the same results. Thanks Nathaniel On 5/30/2012 2:25 PM, Daniel-Constantin Mierla wrote:
Hello, On 5/30/12 9:10 PM, Akan wrote:
This was a re-pull from the git master. I had deleted all of the old files and issued these commands: git clone --depth 1 git://git.sip-router.org/sip-router kamailio cd kamailio git checkout -b 3.2 origin/3.2 This is the source that I got. Could this be a problem within git?
do not checkout branch 3.2, just try with the master branch, as said, not all patches are backported to stable 3.2. For sake of completeness, here are some guidelines: http://www.kamailio.org/wiki/install/devel/git Cheers, Daniel
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org <mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla -http://www.asipto.com http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda> -http://www.linkedin.com/in/miconda Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 -http://asipto.com/u/katu Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 -http://asipto.com/u/kpw _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org <mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
This email is subject to the disclaimer of Smile Communications (PTY) Ltd. at http://www.smilecoms.com/disclaimer