To give a more verbose answer, the line in the backtrace that says no debugging symbols found answers the rest of your question: It's not possible to tell where the signal comes from, because asterisk was built without debugging symbols. This is not a proper backtrace in that it doesn't trace back to anything. So we can't say from this what caused the problem.
Regards, Stephen J Alexander MPBX, LLC http://mpbx.com 832-713-6729 On Fri, May 4, 2012 at 3:58 PM, Doug Lytle <supp...@drdos.info> wrote: > >> is this an answer or is the most of your answer missing ? > > That would be his answer. If you type kill -l, you'll get a listing of > signals: > > kill -l > > 1) SIGHUP 2) SIGINT 3) SIGQUIT 4) SIGILL 5) SIGTRAP > 6) SIGABRT > > 6 would be signal abort. > > Doug > > -- > Ben Franklin quote: > > "Those who would give up Essential Liberty to purchase a little Temporary > Safety, deserve neither Liberty nor Safety." > > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > New to Asterisk? Join us for a live introductory webinar every Thurs: > http://www.asterisk.org/hello > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users