https://bugs.kde.org/show_bug.cgi?id=417075
--- Comment #6 from Philippe Waroquiers <philippe.waroqui...@skynet.be> --- (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). > > 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. Yes, unfortunate. I will add Julian in the cc list to have some more opinions ... > > I wonder if we can make [...] special so that it either matches the literal > string [...] or [<number>]. This can for sure be coded, but the error matching code/logic is IMO quite complex already, and moreover, this logic will be tool and error dependent, as the extra message matching is done by the tool, not by the m_errormgr.c common core module. > > 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.
