You shouldn’t report a segmentation fault unless you actually have a segmentation fault. The evidence you have provided is of cases where the user space software has called abort().
You should not provide the core file. It is of no use to us without the symbol tables.
You should make sure that gdb has access to the debugging symbols, before trying to get the backtrace. These are either included in the executables or in separate files.
If you expect more than a cursory glance at the backtraces, you must reproduce the fault in a current, unmodified, version of Asterisk. If a modified version is essential, you either need to debug down to the actual faulty code, or you need to get the supplier of the modified version to debug it. You appear to have a modified version.
Even for standard, current versions, if the code isn’t compiled with NOOPTIMISE, it may be too difficult to see enough of what is going on to be able to debug it.
Especially where memory corruption is indicated, as in your case, you need to provide a lot of detail as to what was happening at the time, including any unusual message within a few minutes of the crash, as the underlying fault may have been created by code which isn’t on the current stack.