https://bugs.kde.org/show_bug.cgi?id=255704
Kevin Kofler <kevin.kof...@chello.at> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kevin.kof...@chello.at
--- Comment #6 from Kevin Kofler <kevin kofler chello at> 2010-10-31 01:34:03
---
Those reports from Valgrind are only about uninitialized stuff, they don't look
like something that'd crash by itself.
But anyway, a Valgrind log is unlikely to carry any useful information if the
whole system crashed. If the whole system crashes, that sounds like a bug in
the kernel or the graphics drivers. Nothing else on the system has that kind of
low-level access. (So I don't think glibc has anything to do with that issue,
either.) Unfortunately, Valgrind cannot provide information about crashes in
the kernel or kernel modules.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Okular-devel mailing list
Okular-devel@kde.org
https://mail.kde.org/mailman/listinfo/okular-devel
