Summary:	ASTERISK-11706: Core dump from svn trunk build - not sure why
Reporter:	Rick Ross (rickross)	Labels:
Date Opened:	2008-03-23 16:17:49	Date Closed:	2011-06-07 14:00:50
Priority:	Critical	Regression?	No
Status:	Closed/Complete	Components:	Applications/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) asterisk_12283_2.txt ( 1) asterisk_12283_3.txt ( 2) asterisk_12283.txt
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.
Comments:	By: Rick Ross (rickross) 2008-03-23 16:46:29 I let this build run a while longer and had another core dump in less than a half hour. This time I noticed unfo in the CLI log which I had previously missed, and I went back and found the same CLI log info from the first dump. Both are included in the attached "asterisk_12283_3.txt" file. Hope this helps. By: Tilghman Lesher (tilghman) 2008-03-24 07:49:11 Please follow the instructions in doc/valgrind.txt. By: Rick Ross (rickross) 2008-03-24 08:57:17 Sorry, that is more involved than I am willing to get right now. I've tried to be helpful by providing the backtrace data, but rebuilding with a bunch of new options, and waiting for a crash to occur will require more time than I can afford. By: Jason Parker (jparker) 2008-03-28 13:51:58 There is very little chance that any progress will be made here unless we can see valgrind output. By: Clod Patry (junky) 2008-03-29 00:02:05 i am getting a __kernel_vsyscall() too when calling free() in ASTERISK-11690. By: Rick Ross (rickross) 2008-03-29 15:42:35 I tried to do this valgrind and hit a snag attempting to get asterisk-addons to build. There is nothing in the "make menuselect" for asterisk-addons that allows the configuration of compiler options like there is in the "make menuselect" for asterisk itself. My config depends on the asterisk-addons - how do I build them for valgrind? By: Clod Patry (junky) 2008-03-29 15:43:29 valgrind is an external application that you run asterisk in it. By: Rick Ross (rickross) 2008-03-29 17:02:11 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. Others have apparently encountered a similar problem - http://bugs.digium.com/view.php?id=11291 By: Tilghman Lesher (tilghman) 2008-05-19 15:07:30 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. By: Joshua C. Colp (jcolp) 2008-06-02 09:01:20 As Corydon mentioned that issue has been fixed in regards to the compiler flags. Are you now able to acquire what is needed to progress this issue? By: Tilghman Lesher (tilghman) 2008-06-16 11:07:36 Since we have gotten no response, we have to assume that upgrading to the latest version fixed the issue.