On Thu, Jan 21, 2010 at 07:54:50PM +0100, Michael Pilgermann wrote: > To be honest - I haven't got a clue about C++ stuff; debug and so on ... > but I used gdb now in order to get a stack trace - maybe that is help to > somebody: > > > Program received signal SIGSEGV, Segmentation fault. > 0x4074a6f0 in ?? () from /usr/lib/libsyncml.so.2 > (gdb) bt > #0 0x4074a6f0 in ?? () from /usr/lib/libsyncml.so.2 > #1 0x400be322 in ?? () from /usr/lib/libpython2.6.so.1.0 > Backtrace stopped: previous frame identical to this frame (corrupt stack?) > (gdb)
With debuging symbols you I got something a bit different.. SHR r...@gojama /usr/lib $ gdb /usr/bin/python GNU gdb (GDB) 7.0 Copyright (C) 2009 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 "arm-oe-linux-gnueabi". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/bin/python...Reading symbols from /usr/bin/.debug/python...(no debugging symbols found)...done. (no debugging symbols found)...done. (gdb) set args /opt/pisi/pisi.py syncmlMobicalCalendar localIcs (gdb) r Starting program: /usr/bin/python /opt/pisi/pisi.py syncmlMobicalCalendar localIcs [Thread debugging using libthread_db enabled] [New Thread 0x4149f470 (LWP 4612)]....................................................] Loading from sources [New Thread 0x41c9f470 (LWP 4613)] Program received signal SIGILL, Illegal instruction. 0x406c2fb4 in __real_X509_NAME_ENTRY_create_by_txt () from /usr/lib/libcrypto.so.0.9.8 (gdb) bt #0 0x406c2fb4 in __real_X509_NAME_ENTRY_create_by_txt () from /usr/lib/libcrypto.so.0.9.8 #1 0x409b2538 in xmlXPathEqualNodeSets () from /usr/lib/libxml2.so.2 #2 0x409b2538 in xmlXPathEqualNodeSets () from /usr/lib/libxml2.so.2 Backtrace stopped: previous frame identical to this frame (corrupt stack?) > > I got really enthusiastic when I heart about the available syncml libs > > now ... Hehe, they are there for long :) http://lists.openmoko.org/pipermail/community/2009-August/053402.html -- uin:136542059 jid:[email protected] Jansa Martin sip:[email protected] JaMa _______________________________________________ Shr-User mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-user
