On 13-08-26 6:34 PM, Hannes Erven wrote:
Hi Jean,


thank you for your help and sorry for not strictly following the debug guide in
the first place :-/

Here's the new GDB transcript - unfortunately it is quite the same:


$ gdb --args /usr/sbin/sogod -WOUseWatchDog NO -WONoDetach YES -WOPort 20000
-WOWorkersCount 1 -WOLogFile - -WOPidFile /tmp/sogo.pid

GNU gdb (Gentoo 7.5.1 p2) 7.5.1
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.gentoo.org/>...
Reading symbols from /usr/sbin/sogod...(no debugging symbols found)...done.
(gdb) b [NSException raise]
Function "[NSException raise]" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 ([NSException raise]) pending.
(gdb) b abort
Breakpoint 2 at 0x2af0
(gdb) r
Starting program: /usr/sbin/sogod -WOUseWatchDog NO -WONoDetach YES -WOPort
20000 -WOWorkersCount 1 -WOLogFile - -WOPidFile /tmp/sogo.pid
warning: Could not load shared library symbols for linux-gate.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
recursion encountered handling uncaught exception

Breakpoint 2, 0xb7286ad5 in abort () from /lib/libc.so.6
(gdb) bt
#0  0xb7286ad5 in abort () from /lib/libc.so.6
#1  0xb759ba14 in ?? () from /usr/lib/libgnustep-base.so.1.24
#2  0xb740bde8 in objc_msg_lookup () from
/usr/lib/gcc/i686-pc-linux-gnu/4.5.4/libobjc.so.2
#3  0x80002ccc in main ()
(gdb)


This time there was no entry in dmesg.

These binaries were built using the gentoo ebuilds, so perhaps the "debug"
wasn't correctly honoured? Shall I manually rebuild the sources from scratch to
improve chances to a better stacktrace?
We may get a better trace if you had debugging symbols for gnustep-base, but it would be even better if you could build sope + sogo with debugging enabled[1], since we could see exactly where it breaks.

Since your trace shows that it abort() from main(), you could simply step through the instructions with gdb and see where it crashes:

  (gdb) b main
  (gdb) run
  (gdb) n        <--- do this for each instruction until it crashes

Then post the results here :-)


[1] 
http://www.sogo.nu/english/nc/support/faq/article/how-do-i-compile-sogo-2.html



Thanks again, best regards

     -hannes

--
users@sogo.nu
https://inverse.ca/sogo/lists

Reply via email to