[Bug 304605] New: Suggestion: Add a manual page that explains step-by-step how to set up a debugging environment for KDE
joulupukin.tontut at yandex.ru
Sun Aug 5 09:36:08 UTC 2012
Bug ID: 304605
Assignee: kde-www at kde.org
Summary: Suggestion: Add a manual page that explains
step-by-step how to set up a debugging environment for
Reporter: joulupukin.tontut at yandex.ru
Hardware: Gentoo Packages
I reported a bug on plasma crashing when I try to open the desktop settings
(bug 304172). Now, because I have some programming experience, I thought I
could help to debug this myself. However, I failed, because I can't figure out
how to set up a n adequate compile and debug environment. There are a couple of
documents on the KDE web pages, but all of them address just parts of this
issue, and some steps are missing. (List below.) So, I wonder, could someone
write a step-by-step instruction for what to do to achieve the following?
Starting point: Assume the user has a working KDE environment, and that he
doesn't want to break that.
Target: The user should be able to run (maybe in a chroot or in a separate
account etc) the KDE environment within a debugger so that, when something
fails, it's possible to "step into" the code and look at what are the values of
variables, what's on the call stack, which line in the source code it is, etc.
It must be also possible to adjust the source code, recompile, and run that.
Here are all the documents that I looked at. I figured out how to compile
particular KDE components successfully, but I could not figure out how to (a)
make my system use the freshly compiled libraries without breaking the rest of
the system, (b) what kind of things I should do with a different user account
so I don't break my current account, (c) start KDE desktop from within a
Reproducible: Didn't try
You are receiving this mail because:
You are the assignee for the bug.
More information about the kde-www