[Nepomuk] Problem with storage crashing repeatedly

[Lindsay Mathieson]

On Fri, 21 Jun 2013 04:59:48 PM you wrote:
> Start nepomukstorage and see what command line parameters virtuoso is
> called with.


That was giving me problems - storage didn't seem to like it, until I had the 
bright idea of just attaching to the exisitng process ...

This is what I got when virtuoso crashed:

(gdb) continue
Continuing.
[New Thread 0x7fa0d53e5700 (LWP 7641)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fa0d546f700 (LWP 7603)]
0x0000000000975b8b in ?? ()
(gdb) continue
Continuing.
[Thread 0x7fa0f22fb700 (LWP 7590) exited]
[Thread 0x7fa0d53e5700 (LWP 7641) exited]
[Thread 0x7fa0d5583700 (LWP 7593) exited]
[Thread 0x7fa0d54f9700 (LWP 7602) exited]
[Thread 0x7fa0d546f700 (LWP 7603) exited]
[Thread 0x7fa0f22c9740 (LWP 7589) exited]

Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.


Doesn't seem like any better info unfortunately
-- 
Lindsay
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/nepomuk/attachments/20130622/f0ddc972/attachment.sig>