Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 21 Feb 2016 23:55:21 +0100
From:      Andreas Longwitz <longwitz@incore.de>
To:        Hans Petter Selasky <hps@selasky.org>
Cc:        freebsd-isdn@freebsd.org
Subject:   Re: chan_capi error after update
Message-ID:  <56CA4059.7060601@incore.de>
In-Reply-To: <56C895EA.5000404@selasky.org>
References:  <56C6E0D4.5060603@incore.de> <56C74704.6060606@selasky.org> <56C83752.6080708@selasky.org> <56C87494.6020605@incore.de> <56C87F06.1070504@selasky.org> <56C88301.3060104@selasky.org> <56C89326.4030803@incore.de> <56C895EA.5000404@selasky.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi,


> Looks good to me. What happens when you try to dial IN/OUT. Nothing works?
> And did you try "capitest" to make a CAPI test call?
> Can you describe a bit more what is not working?
> 
> --HPS

On first dial OUT asterisk crashed with core dump and therefore I first
tried to get rid of the messages

  ERROR[988] chan_capi.c: CAPI error sending CAPI_FACILITY_REQ

In the meantime I have inspected the core dumps and found the crash
happens in the library libexecinfo.so.1, which is activated by asterisk
because I have

  ASTCFLAGS+=-DDEBUG_THREADS -DBETTER_BACKTRACES -DNO_OPTIMIZE

in the configure step. Then I found PR/193610 which includes your
comment to the compiler flag "-fno-omit-frame-pointer". After adding
this flag to the asterisk18 Makefile the dumps are gone and on my
(small) test machine everything works as expected.

Maybe it is better to use this flag for chan_capi too ?


-- 
Andreas Longwitz




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56CA4059.7060601>