https://bugs.kde.org/show_bug.cgi?id=417075
--- Comment #5 from Mark Wielaard <m...@klomp.org> --- 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 variant of the error message. So we would indeed break some existing suppressions picking either the old or new variant. I wonder if we can make [...] special so that it either matches the literal string [...] or [<number>]. Note: we do use the [...] variant also in [process_vm_](readv|writev) and vmsplice. -- You are receiving this mail because: You are watching all bug changes.
