|Summary:||ASTERISK-03183: Asterisk Core dumps upon reload, Not always|
|Reporter:||Alberto Fernandez (derkommissar)||Labels:|
|Date Opened:||2005-01-05 00:39:45.000-0600||Date Closed:||2011-06-07 14:10:42|
|Environment:||Attachments:||( 0) CoreDump|
|Description:||Please look at the core dump|
|Comments:||By: Kevin P. Fleming (kpfleming) 2005-01-05 07:56:06.000-0600|
Please update to more recent CVS HEAD and re-test.
By: alric (alric) 2005-01-05 13:30:29.000-0600
Also, the coredump itself is less than useful. If this happens again after you update to CVS, run a backtrace on the core dump and post it here. If you don't know how to do backtraces, just find a bug marshall on IRC and they can help you.
By: Kevin P. Fleming (kpfleming) 2005-01-05 13:38:16.000-0600
And if you intend to do a backtrace, you should build Asterisk using "make valgrind" to doubly ensure that all the debugging information ends up in the binaries you are running.
By: Olle Johansson (oej) 2005-01-08 04:06:59.000-0600
afernandez: Does this still happen with latest CVS? Any backtrace?
By: Mark Spencer (markster) 2005-01-12 23:49:20.000-0600
One more try, is this still a problem with CVS head, and can you supply a backtrace with "make clean ; make valgrind ; make install"?
By: Russell Bryant (russell) 2005-01-18 20:33:42.000-0600
poster seems to have lost interest ...