Hello,
what does it mean when you read in the backtrace file :
Reading symbols from /lib64/libgcc_s.so.1...(no debugging symbols
found)...done.
Loaded symbols for /lib64/libgcc_s.so.1
Core was generated by `/usr/sbin/asterisk -f -vvvg -c'.
Program terminated with signal 6, Aborted.
#0 0x0
On Fri, 4 May 2012, Jonas Kellens wrote:
Terminated with signal 6, what is that ?
kill -l
--
Thanks in advance,
-
Steve Edwards sedwa...@sedwards.com Voice: +1-760-468-3867 PST
Newline
Hello,
is this an answer or is the most of your answer missing ?
I don't understand what you mean and I still don't understand what
happened with Asterisk.
Kind regards,
Jonas.
On 05/04/2012 09:18 PM, Steve Edwards wrote:
On Fri, 4 May 2012, Jonas Kellens wrote:
Terminated with signal 6
>> 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
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
I have selected " don't optimize " in the menuselect for better
information in the trace and now you tell me that it's still useless ?
(off course the trace created with bt full is more verbose, but I cant'
post all that)
Kind regards,
Jonas.
On 05/04/2012 11:08 PM, Stephen J Alexander wro
On Fri, May 04, 2012 at 08:34:49PM +0200, Jonas Kellens wrote:
> Hello,
>
> what does it mean when you read in the backtrace file :
>
> Reading symbols from /lib64/libgcc_s.so.1...(no debugging symbols
> found)...done.
No debugging symbols are avaialble for libgcc_s . Libgcc is an external
libra
On Fri, May 04, 2012 at 11:53:41PM +0200, Jonas Kellens wrote:
> I have selected " don't optimize " in the menuselect for better
> information in the trace and now you tell me that it's still useless
> ?
(As mentioned in a separate post, this is not related to the missing
debug symbols from the ex
