https://bugs.kde.org/show_bug.cgi?id=484019
--- Comment #15 from Jiri Palecek <jpale...@web.de> --- (In reply to Thomas Berger from comment #14) > Sorry for the confusion, of course i was talking about libksysguard. I don't > know why, but somehow i dropped the "lib" prefix. > > To be able to debug this, i need a debug build of both parts, but the build > system makes this hard for me right now, as i am unable to generate a > appropriate *Targets.cmake file from the build directory of my libksysguard > debug builds, as generated with the install paths only. Oh. I never needed any of that. I can only suggest: - what is your distribution? Maybe it already has debug symbol packages installable. (eg. debian -> libksysguardsystemstats2-dbgsym) - do you really need to build ksystemstats with rpath? If not, you don't need to worry about any Targets.cmake files, just point to the debugging libraries with LD_LIBRARY_PATH=/path/to/libksysguard-src/.../bin ksystemstats ... - maybe, you don't need to debug libksysguard. Can you 100% ensure that this point is true > 4. After the call to KSysGuard::SensorsFeatureSensor::update() a call to > ::value() returns an invalid QVariant. specifically, that it calls update() on the correct sensor? You could just place a breakpoint in sensors_get_value from libsensors and check the return value. Or, if you have ltrace, you could run ltrace -e sensors_get_value@* ksystemstats ... to see at least if there aren't any errors. -- You are receiving this mail because: You are watching all bug changes.
