[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:              03-29-2008 17:02 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.
====================================================================== 

---------------------------------------------------------------------- 
 rickross - 03-29-08 17:02  
---------------------------------------------------------------------- 
The menuselect for asterisk provides a way to set the compiler options
MALLOC_DEBUG and DONT_OPTIMIZE as specified in the valgrind instructions
doc.

The menuselect for asterisk-addons provides no such options, and I don't
know how to set them manually. The addons cannot be loaded unless they are
built compatibly with asterisk, itself.

I can't provide a useful valgrind log unless I can get the asterisk-addons
built and loaded successfully. They are required for my configuration to
run correctly. IMO, there should be a way to set compiler options for
asterisk-addons via menuselect in a way that parallels the menuselect
compiler options for the main asterisk. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
03-29-08 17:02  rickross       Note Added: 0084759                          
======================================================================