Your message dated Thu, 06 Jul 2006 07:28:57 +0200
with message-id <[EMAIL PROTECTED]>
and subject line pth: make test fails on ARM
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: jabber
Version: 1.4.2a-1
Severity: normal
Greetings,
After installing the Jabber package, it appears that it segfaults
immediately on start up.
Actually it doesn't APPEAR to break, however it is not running after
the init.d script say that it started. Further debugging revealed that
the server may be segfaulting at startup. I have tried this with both
the default configs and combinations of local config (even if it is a
bad config, it doesn't seem like it should segfault).
thanks.
-- Here is a log of things:
Script started on Fri Apr 12 21:07:12 2002
ixchel:~# /etc/init.d/jabber start
Starting jabberd: jabberd.
ixchel:~# ps awx |grep jabberd
10116 pts/1 S 0:00 grep jabberd
ixchel:~# jabberd
A pidfile already exists at the specified location. Check to ensure
another copy of the server is not running, or remove the existing file.
ixchel:~# rm /var/run/jabber/jabber.pid
ixchel:~# jabberd
Segmentation fault
ixchel:~# rm /var/run/jabber/jabber.pid
ixchel:~# gdb jabberd
GNU gdb 5.1.1
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and
you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for
details.
This GDB was configured as "arm-linux"...(no debugging symbols found)...
(gdb) run
Starting program: /usr/sbin/jabberd
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
Program received signal SIGUSR1, User defined signal 1.
0x4017590c in sigsuspend () from /lib/libc.so.6
(gdb) backtrace
#0 0x4017590c in sigsuspend () from /lib/libc.so.6
#1 0x00054df0 in __pth_mctx_set ()
#2 0x00054370 in pth_spawn ()
#3 0x00053e20 in pth_init ()
#4 0x00019628 in main ()
#5 0x401624b4 in __libc_start_main () from /lib/libc.so.6
(gdb) The program is running. Exit anyway? (y or n) y
ixchel:~#
Script done on Fri Apr 12 21:08:26 2002
-- System Information
Debian Release: 3.0
Architecture: arm
Kernel: Linux ixchel 2.4.16 #1 Mon Dec 24 13:12:36 GMT 2001 armv4l
Locale: LANG=C, LC_CTYPE=C
Versions of packages jabber depends on:
ii libc6 2.2.5-4 GNU C Library: Shared libraries an
ii libssl0.9.6 0.9.6c-2 SSL shared libraries
--
-><- Nick Rusnov
-><- http://nick.industrialmeats.com
-><- [EMAIL PROTECTED]/[EMAIL PROTECTED]
--- End Message ---
--- Begin Message ---
Hi,
this bug is resolved with the newer upstream version uploaded recently.
Regards,
Daniel
--
Address: Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email: [EMAIL PROTECTED]
Internet: http://people.panthera-systems.net/~daniel-baumann/
--- End Message ---
