Bug 98290

Summary:	Valgrind internals need annotating
Product:	[Developer tools] valgrind	Reporter:	Jeremy Fitzhardinge <jeremy>
Component:	general	Assignee:	Julian Seward <jseward>
Status:	REPORTED ---
Severity:	minor	CC:	info, tom
Priority:	NOR
Version First Reported In:	2.3 CVS
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
URL:	https://invent.kde.org/kdevelop/kdev-valgrind
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Jeremy Fitzhardinge 2005-01-31 19:07:22 UTC

We need to annotate Valgrind's internals, so that we can usefully run it under
itself and find bugs.  The #1 priority is obviously the memory allocator.

I looked at it, but I don't really understand how it works, so I'm hoping
someone who does (Nick? Julian?) can look at it when they get a chance.

Comment 1 Nicholas Nethercote 2005-02-02 00:37:51 UTC

I'm happy to look -- I want to work on improving our testing -- but I won't have time for a while, at least a few weeks.

Comment 2 T I Z E N 2025-02-17 18:57:17 UTC

If the origin Members still active on this or have an Ticket, MR or PR (as in Invent or on the Kanban), can you insert it to the Bug Report?
Thank you for the bug report. Unfortunately we were not able to get to it yet. Can we ask you to please check if this is still an issue with either Plasma 5.27 (the current LTS version) or Plasma 6.3 (the latest released version).

Comment 3 Tom Hughes 2025-02-17 19:11:50 UTC

Valgrind is a guest in the KDE bug tracker but it does not use KDE development processes so please ignore that last comment.

Comment 4 T I Z E N 2025-02-17 19:14:49 UTC

(In reply to Tom Hughes from comment #3)
> Valgrind is a guest in the KDE bug tracker but it does not use KDE
> development processes so please ignore that last comment.

Woops. I apologize for the misstep. I will adjust this accordingly for the future.