[Spce-user] found sems had stopped

[Theo]

Hi

Not sure if that gave me more than what I had?

Core was generated by `/usr/sbin/sems -P /var/run/sems/sems.pid -u sems -g
sems -f /etc/sems/sems.conf'.
Program terminated with signal 6, Aborted.
#0  0x00007f907dccb1b5 in ?? ()
(gdb) bt full
#0  0x00007f907dccb1b5 in ?? ()
No symbol table info available.


No idea what this means.

On Mon, Feb 16, 2015 at 9:00 AM, Jon Bonilla (Manwe) <manwe at sipdoc.net>
wrote:

> El Fri, 13 Feb 2015 10:53:00 +0200
> Theo <axessofficetheo at gmail.com> escribió:
>
> > Ok found :
> >
> > Program terminated with signal 6, Aborted.
> >
> > which is a little over my head I'm afraid. How does on interpret this?
> >
> >
>
> install the sems debug package and gdb:
>
> apt-get install ngcp-sems-dbg gdb
>
>
> Then run gdb:
>
> gdb /usr/sbin/sems core.sems.sig6.24219
>
>
>
> once there run "bt full" to get the info.
>
>
>
>  https://wiki.debian.org/HowToGetABacktrace
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20150216/68d9a1b4/attachment-0001.html>