https://bugs.kde.org/show_bug.cgi?id=405394
Daniel Wagner changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=405394
zephyrus00jp changed:
What|Removed |Added
CC||ishik...@yk.rim.or.jp
--- Comment #7 from zephyr
https://bugs.kde.org/show_bug.cgi?id=405394
--- Comment #6 from Daniel Wagner ---
I am not sure if I handle the size argument correctly. Here the snipped from
the man pages:
size This field should be set to the size of the structure in
bytes, as in
sizeof(struct
https://bugs.kde.org/show_bug.cgi?id=405394
Daniel Wagner changed:
What|Removed |Added
Attachment #118743|0 |1
is obsolete|
https://bugs.kde.org/show_bug.cgi?id=405394
--- Comment #4 from Tom Hughes ---
Well that one doesn't need a PRE_MEM_READ so the fact that it would complain
isn't really relevant.
You should use PRE_MEM_READ before the system call for any memory which will be
read by the system call and PRE_MEM_W
https://bugs.kde.org/show_bug.cgi?id=405394
--- Comment #3 from Daniel Wagner ---
With PRE_MEM_READ valgrind will complain for code like this (which should be
fine, right?):
void run_deadline() {
struct sched_attr attr;
https://bugs.kde.org/show_bug.cgi?id=405394
--- Comment #2 from Daniel Wagner ---
Thanks for the feedback.
Okay, sorry for those obvious bugs. I was in a too fast copy&past mode. I'll
update the patch accordingly, tomorrow.
--
You are receiving this mail because:
You are watching all bug chang
https://bugs.kde.org/show_bug.cgi?id=405394
Tom Hughes changed:
What|Removed |Added
CC||t...@compton.nu
--- Comment #1 from Tom Hughes --
