On Fri, Jan 22, 2010 at 03:58:16PM +0100, Martin Jansa wrote: > 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..
more info here http://pastebin.ca/1761592 I don't have spare time this week or so.. but I asked pb for help, his expirienced eye can see thumb interworking problems even with quick glance :). Cheers, -- 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
