[asterisk-bugs] [Asterisk 0012283]: Core dump from svn trunk build - not sure why

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12283 
====================================================================== 
Reported By:                rickross
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12283
Category:                   Applications/General
Reproducibility:            have not tried
Severity:                   crash
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 110609 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             03-23-2008 16:17 CDT
Last Modified:              05-19-2008 15:07 CDT
====================================================================== 
Summary:                    Core dump  from svn trunk build - not sure why
Description: 
I built from svn trunk revision 110609 to test a resolution to a previous
core dumping issue (ID 12225). Everything seemed fine for a while, but
later I noticed I had a different core dump with the new build. I grabbed a
backtrace with gdb, but it means little to me. I had reinstalled 1.6.0beta4
after the core dump, but switched back to the svn trunk build to load gdb,
hence the message that the exec is newer than the core dump. The correct
asterisk was loaded for gdb.
====================================================================== 

---------------------------------------------------------------------- 
 Corydon76 - 05-19-08 15:07  
---------------------------------------------------------------------- 
Please attempt to rebuild with the latest trunk -- there was an issue as
you correctly pointed out, but it has been fixed now.  You may need to do a
'make clean' in your -addons directory before this will work properly,
though.

The DONT_OPTIMIZE and other flags are inherited from the installed version
of Asterisk, as they have to match exactly in order to work correctly. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
05-19-08 15:07  Corydon76      Note Added: 0087031                          
======================================================================