[Home]

Summary:ASTERISK-13823: Asterisk crashes on incoming call that is hung up before answered.
Reporter:Frederic Van Espen (freh)Labels:
Date Opened:2009-03-25 06:11:20Date Closed:2011-06-07 14:00:35
Priority:CriticalRegression?No
Status:Closed/CompleteComponents:Channels/chan_misdn
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) gdb.txt
( 1) gdb-unstripped.txt
Description:I have asterisk set up with a Digium B410P isdn card. I use the mISDN driver for the card (version 1.1.9-1)

I have my phonenumbers forwarded to certain SIP phones. When I make an incoming call from my cellphone and hang up before the phone is answered, asterisk sometimes crashes.

I have attached output from gdb with bt, bt full and thread apply all bt
Comments:By: David Woolley (davidw) 2009-03-25 06:26:19

You've used a stripped binaries.  The backtrace isn't going to be of any real use.

If you have the unstripped binaries from which the stripped ones were created, specify the unstripped asterisk as the executable to gdb, and make sure it knows where to find the unstripped modules.  However to be of any real use, it will need to have been compiled with the NOOPTIMISE build option.

Note that the official build tools do not create a stripped binary.
By: Frederic Van Espen (freh) 2009-03-25 07:38:34

I did compile it with NOOPTIMISE option. i.e I did a "make menuselect" and selected DEBUG_THREADS DONT_OPTIMIZE. I don't get why i have stripped binaries. I used the normal debian build tools.
By: David Woolley (davidw) 2009-03-25 08:57:44

Looks like configure might do that if you already had an INSTALL environment variable and it included the strip option.
By: Frederic Van Espen (freh) 2009-03-25 11:08:06

Ok it appears checkinstall was stripping the binaries. I always make deb packages. Anyway, I attached the usable core dump. It appears to be a problem with mISDN...
By: Russell Bryant (russell) 2009-10-05 21:33:32

I'm going to suspend this issue for now.  It has been a while since anyone has touched this, and unfortunately, there is not much we can do with the backtraces.

If you still have this problem with the latest version of Asterisk, please open a new report.  Also, it would be extremely useful if you could run under valgrind and post the output (see doc/valgrind.txt).

Thanks