https://bugs.kde.org/show_bug.cgi?id=365208
Philippe Waroquiers <philippe.waroqui...@skynet.be> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |philippe.waroquiers@skynet.
| |be
--- Comment #1 from Philippe Waroquiers <philippe.waroqui...@skynet.be> ---
With just the provided info, there is not much we can say.
Several things can be done to investigate what goes wrong:
1. add some traces e.g. start valgrind with
-v -v -v -d -d -d
2. assuming that your application is started up, you can investigate what it is
doing under valgrind
using valgrind+vgdb + gdb.
3. finally, you could try to debug valgrind itself by using gdb and attach to
the memcheck-ppc32 program, do a backtrace and report what it does
--
You are receiving this mail because:
You are watching all bug changes.
