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

[noreply at bugs.digium.com]

The following issue has been CLOSED 
====================================================================== 
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:                     closed
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:              
Resolution:                 no change required
Fixed in Version:           
====================================================================== 
Date Submitted:             03-23-2008 16:17 CDT
Last Modified:              06-16-2008 11: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 - 06-16-08 11:07  
---------------------------------------------------------------------- 
Since we have gotten no response, we have to assume that upgrading to the
latest version fixed the issue. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-16-08 11:07  Corydon76      Note Added: 0088761                          
06-16-08 11:07  Corydon76      Status                   feedback => closed  
06-16-08 11:07  Corydon76      Resolution               open => no change
required
======================================================================