[Home]

Summary:ASTERISK-16511: core dump in ast_cdr_getvar
Reporter:Marcello Ceschia (marcelloceschia)Labels:
Date Opened:2010-08-05 05:09:22Date Closed:2011-06-07 14:01:05
Priority:CriticalRegression?No
Status:Closed/CompleteComponents:CDR/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) backtrace.txt
Description:during an incomming call asterisk (svn r280623) crashed with coredump.
somthing strange:
-cid_name=0x81b0fa0 "ast_udptl_proto_register"
-acctcode=0x81b0fa0 "ast_udptl_proto_register"
-chan = 0x818beb9 "ion Allowed, Failed Screen"

****** ADDITIONAL INFORMATION ******

backtrace removed - pabelanger
Comments:By: Marcello Ceschia (marcelloceschia) 2010-08-05 05:12:42

I forgot, it is svn branch 1.6.2



By: Paul Belanger (pabelanger) 2010-08-05 05:46:02

Please upload your backtraces, don't post them as notes.  It helps to keep the issue clean.
---
Thank you for your bug report. In order to move your issue forward, we require a backtrace from the core file produced after the crash. Please see the doc/backtrace.txt file in your Asterisk source directory.

Also, be sure you have DONT_OPTIMIZE enabled in menuselect within the Compiler Flags section, then:

make install

after enabling, reproduce the crash, and then execute the instructions in doc/backtrace.txt.

When complete, attach that file to this issue report. Thanks!

By: Marcello Ceschia (marcelloceschia) 2010-08-05 07:02:12

@pabelanger thank you for your advice, DONT_OPTIMIZE is already enabled

By: Tilghman Lesher (tilghman) 2010-08-05 10:35:40

Your backtrace appears to contain memory corruption and we require valgrind output in order to move this issue forward.

Please see the doc/valgrind.txt file in your Asterisk source directory for more information about how to produce debugging information. Thanks!

By: Paul Belanger (pabelanger) 2010-08-18 07:58:30

Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested.

Further information can be found at http://www.asterisk.org/developers/bug-guidelines