Hi, Nepoogle is a python script and not an executable. This is GDB output:
Starting program: No executable file specified. Use the "file" or "exec-file" command. But I'm sure that better than a backtrace is a method to reproduce the crash: #!/usr/bin/env python # -*- coding: utf-8 -*- from PyKDE4.nepomuk import * uri = "nepomuk:/res/1f8e139e-3153-4fce-9797-d8bdb8c18d40" print Nepomuk.Resource(uri).resourceType().toString() uri could be a existing or not existing uri and, off course, this code works in console and crash in a ssh session. But I think that this crash is not relevant, except maybe to discover that there is a coding bug that could be affect other Nepomuk's process, because I'm totally sure that I'm the only person queering his Nepomuk database in a ssh session and I solved the crash using a workaround. But I think that we are loosing my original question, where is the code that determine the value of the resourceType property? On Mon, Apr 30, 2012 at 5:40 PM, Martin Klapetek <[email protected]>wrote: > On Mon, Apr 30, 2012 at 15:20, Ignacio Serantes <[email protected]> wrote: > >> No, because crash is in a remote session so there is no Dr.konky. > > > If you have gdb, you can run nepoogle in it and then generate a backtrace: > > $ gdb nepoogle > gbd> run > (...crash...) > gdb> bt > > Here comes the backtrace. > > -- > Martin Klapetek | KDE Developer > -- Best wishes, Ignacio
_______________________________________________ Nepomuk mailing list [email protected] https://mail.kde.org/mailman/listinfo/nepomuk
