I followed the instructions at
openSUSE:Bugreport KDE - openSUSE
to install debug symbols for okular which seems to crash quite often for me. However gdb and the kde crash application are unable to find them. The kde app says its not a good crash report and I should follow the guide… which has already been done.
is there a step i’m missing to get gdb to load the symbols or something?
Just guessing: wouldn’t you need the okular-debuginfo or debugsource package?
YaST>System>Software repositories - you may find that you have the debug repository in your list but not enabled. Add it if it is not there or enable it if it is.
I was missing the okular debug package but added that as well and still no luck… here is my output
spoofy@shell:~> rpm -qa | grep debuginfo
spoofy@shell:~> gdb /usr/bin/okular
GNU gdb 6.8
Copyright (C) 2008 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 "x86_64-unknown-linux-gnu"...
(no debugging symbols found)
is it possiby a path issue? I noticed the debuginfo package installed /usr/lib/debug/usr/bin/okular.debug which is a binary … but i’m unable to execute it.
Try enabling the debug repository and then updating.
It is enabled
spoofy@shell:~> sudo zypper repos
# | Alias | Name | Enabled | Refresh
1 | Packman_1 | Packman | Yes | No
2 | VirtualBox | VirtualBox | Yes | Yes
3 | debug_repo | debug repo | Yes | Yes
4 | driver:wireless_1 | driver:wireless | Yes | Yes
5 | google-chrome | google-chrome | Yes | Yes
6 | openSUSE-11.3 11.3-1.82 | openSUSE-11.3 11.3-1.82 | Yes | No
7 | repo-debug | openSUSE-11.3-Debug | Yes | Yes
8 | repo-non-oss | openSUSE-11.3-Non-Oss | Yes | Yes
9 | repo-oss | openSUSE-11.3-Oss | Yes | Yes
10 | repo-source | openSUSE-11.3-Source | No | Yes
11 | repo-update | openSUSE-11.3-Update | Yes | Yes
interesting info … valgrind is able to load symbols just fine … gdb doesn’t