On 13-08-25 9:00 PM, Hannes Erven wrote:
Program received signal SIGABRT, Aborted.
0xffffe424 in __kernel_vsyscall ()
(gdb) bt
#0 0xffffe424 in __kernel_vsyscall ()
#1 0xb72856d9 in raise () from /lib/libc.so.6
#2 0xb7286c53 in abort () from /lib/libc.so.6
#3 0xb759ba14 in ?? () from /usr/lib/libgnustep-base.so.1.24
#4 0xb740bde8 in objc_msg_lookup () from
/usr/lib/gcc/i686-pc-linux-gnu/4.5.4/libobjc.so.2
#5 0x80002ccc in main ()
I then tried manually compiling the latest sogo/sope 2.0.7 from the tarballs and
gnustep-base 1.24.5 , which resulted again in a different
but still a segfault on startup:
#1 0xb79f615f in GSToUnicode
(no more details from gdb)
And in dmesg:
[kernel] sogod[1782]: segfault at bf2f0e9c ip b717e15f sp bf2f0ea0 error
6 in libgnustep-base.so.1.24.5[b6ec1000+3a2000]
This is strange. Can you try starting GDB/sogo with the following arguments:
gdb --args /usr/sbin/sogod -WOUseWatchDog NO -WONoDetach YES -WOPort 20000
-WOWorkersCount 1 -WOLogFile - -WOPidFile /tmp/sogo.pid
and then set breakpoints on [NSException raise] and 'abort'
(see http://www.sogo.nu/english/nc/support/faq/article/how-do-i-debug-sogo.html)
Hopefully we'll get a better backtrace with this.
--
[email protected]
https://inverse.ca/sogo/lists
