[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde
Subject:    Re: [kde] Segmentation fault in soprano
From:       Kevin Krammer <kevin.krammer () gmx ! at>
Date:       2012-02-26 13:02:14
Message-ID: 201202261402.15119.kevin.krammer () gmx ! at
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Sunday, 2012-02-26, Dimitar Popov wrote:
> Hi all,
> 
> I found the following thread:
> http://lists.kde.org/?t=132932694700004&r=1&w=2 but I can't reply there
> since I just got subscribed to the mailing list... So, please, apologize
> me for starting a new thread... :)
> 
> I compiled the soprano and kdebase-runtime with debug symbols and I
> attached to all nepomukservicestub process with gdb -p <PID> and here what
> I got for nepomukservicestub nepomukstorage:
> 
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7f19b97fa700 (LWP 5814)]
> 0x00007f19ef2ddeef in Soprano::Node::toN3 (this=<optimized out>) at
> /home/insane/Development/oss/archlinux/extra/soprano/src/soprano-2.7.4/sopr
> ano/node.cpp:252 252         return d ? d->toN3() : QString();
> 
> Yes, it's not a complete stack trace, but I'm new to gdb and I don't know
> how to get a useful stack trace.

You can typ typing bt or bt full on the gdb prompt

Cheers,
Kevin

-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring

["signature.asc" (application/pgp-signature)]

___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

[prev in list] [next in list] [prev in thread] [next in thread]