https://bugs.kde.org/show_bug.cgi?id=417075
Leonid Yuriev changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment #13 from Leonid Yuriev ---
https://bugs.kde.org/show_bug.cgi?id=417075
Philippe Waroquiers changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=417075
--- Comment #11 from Philippe Waroquiers ---
Updated the warning message to be:
==3170== WARNING: preadv(vector[...]) is an obsolete suppression line not
supported anymore since valgrind 3.15.
==3170== You should replace [...] by a specific index such a
https://bugs.kde.org/show_bug.cgi?id=417075
--- Comment #10 from Philippe Waroquiers ---
Some further notes:
I should re-update the warning to replace the final 'or ...'
by 'or [2].
And I sincerely hope that nobody is using preadv and pwritev wrongly
with huge vectors, as otherwise they might n
https://bugs.kde.org/show_bug.cgi?id=417075
--- Comment #9 from Philippe Waroquiers ---
Created attachment 127809
--> https://bugs.kde.org/attachment.cgi?id=127809&action=edit
not a fix, but detects the incompatible supp entry and produce a warning
The commit log explains in details what we en
https://bugs.kde.org/show_bug.cgi?id=417075
--- Comment #8 from Leonid Yuriev ---
Related to https://github.com/erthink/libmdbx/issues/82
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=417075
--- Comment #7 from Philippe Waroquiers ---
(In reply to Mark Wielaard from comment #5)
> This is unfortunate and an unforeseen consequence of making the the error
> message more useful (it is useful to know which vector contained
> uninitialised bytes)
https://bugs.kde.org/show_bug.cgi?id=417075
Philippe Waroquiers changed:
What|Removed |Added
CC||jsew...@acm.org
--
You are receiving thi
https://bugs.kde.org/show_bug.cgi?id=417075
--- Comment #6 from Philippe Waroquiers ---
(In reply to Mark Wielaard from comment #5)
> This is unfortunate and an unforeseen consequence of making the the error
> message more useful (it is useful to know which vector contained
> uninitialised bytes)
https://bugs.kde.org/show_bug.cgi?id=417075
--- Comment #5 from Mark Wielaard ---
This is unfortunate and an unforeseen consequence of making the the error
message more useful (it is useful to know which vector contained uninitialised
bytes).
Sadly we have had releases with both the old and new
https://bugs.kde.org/show_bug.cgi?id=417075
Philippe Waroquiers changed:
What|Removed |Added
CC||ahajk...@redhat.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=417075
Philippe Waroquiers changed:
What|Removed |Added
CC||m...@klomp.org
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=417075
--- Comment #4 from Philippe Waroquiers ---
(In reply to Leonid Yuriev from comment #3)
> > What does `valgrind --gen-suppressions=all ...` show ?
> {
>
>Memcheck:Param
>pwritev(vector[0])
>fun:pwritev
>fun:mdbx_pwritev
>fun:mdbx
https://bugs.kde.org/show_bug.cgi?id=417075
--- Comment #3 from Leonid Yuriev ---
> What does `valgrind --gen-suppressions=all ...` show ?
{
Memcheck:Param
pwritev(vector[0])
fun:pwritev
fun:mdbx_pwritev
fun:mdbx_flush_iov
fun:mdbx_page_flush
fun:mdbx_txn_commit
fun:_Z
https://bugs.kde.org/show_bug.cgi?id=417075
Philippe Waroquiers changed:
What|Removed |Added
CC||philippe.waroquiers@skynet.
https://bugs.kde.org/show_bug.cgi?id=417075
--- Comment #1 from Leonid Yuriev ---
Actual memcheck version information:
==151028== Memcheck, a memory error detector
==151028== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==151028== Using Valgrind-3.15.0 and LibVEX; rerun with -
16 matches
Mail list logo