[apport] s2s crashed with SIGSEGV in __libc_start_main()

Bug #114316 reported by David Grossberg
2
Affects Status Importance Assigned to Milestone
jabberd2 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: jabberd2

This problem has existed since at least Breezy. I actually have a script set up to re-launch this process every time it fails so that I can stay logged in to Jabber, but now that I have apport I can submit an actual bug report with actual debug info.

Note: I suggest simply upgrading to the latest upstream version, the current one is Very old.

If any more information is needed, please let me know.

ProblemType: Crash
Architecture: amd64
Date: Sat May 12 01:41:48 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/s2s
Package: jabberd2 2.0s8-0ubuntu7
PackageArchitecture: amd64
ProcCmdline: /usr/bin/s2s -c /etc/jabberd2/s2s.xml
ProcCwd: /root
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_US.UTF-8
 LANGUAGE=en
Signal: 11
SourcePackage: jabberd2
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 __libc_start_main () from /lib/libc.so.6
 ?? ()
Uname: Linux xinul64x2.davidgro.com 2.6.20-15-generic #2 SMP Sun Apr 15 06:17:24 UTC 2007 x86_64 GNU/Linux
UserGroups:

Revision history for this message
David Grossberg (davidgro) wrote :
Revision history for this message
Martin Pitt (pitti) wrote : Symbolic stack trace

StacktraceTop:xhash_iter_get (h=0x64def0, key=0x7fff00000000, val=0x7ffff8043418) at xhash.c:304
_s2s_time_checks (s2s=0x63b040) at main.c:297
main (argc=<value optimized out>, argv=<value optimized out>) at main.c:557
__libc_start_main () from /lib/libc.so.6
_start ()

Revision history for this message
Martin Pitt (pitti) wrote : Symbolic threaded stack trace
Changed in jabberd2:
importance: Undecided → Medium
Revision history for this message
Kjell Braden (afflux) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Changed in jabberd2:
status: New → Invalid
status: Invalid → Incomplete
Revision history for this message
David Grossberg (davidgro) wrote :

I appears to be working now. I re-setup Jabberd2 and it is logged in from pidgin. Has been for a couple weeks. (Although for some reason gmail seems to think that account is offline, it can still IM it and get back the autoresponse.)

Revision history for this message
Kjell Braden (afflux) wrote :

Closing as it does not seem to be an issue anymore.

Changed in jabberd2:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.