Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 366881

Summary:	Valgrind version number unreliable for new features
Product:	[Tools] Linux Tools	Reporter:	Elliott Baron <ebaron>
Component:	Valgrind	Assignee:	Elliott Baron <ebaron>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3
Version:	0.9.0
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:	stalebug

Description Elliott Baron

2011-12-15 16:26:10 EST

In Ubuntu 10.04, the Valgrind package is an SVN build that is missing the pages-as-heap Massif option available in Valgrind 3.6. The version string for Valgrind is valgrind-3.6.0.SVN-Debian. This causes Massif runs to fail. As a solution, we should only output command line options for options whose value has changed from the default. This will allow Massif to run successfully, even in this pseudo 3.6 build of Valgrind. If the user changes the pages-as-heap option, the run will fail and an error will be shown in the console. They should easily figure out to uncheck that option.

Comment 1 Eclipse Genie

2014-06-03 08:31:33 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 2 Eclipse Genie

2016-05-24 13:02:15 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 3 Eclipse Genie

2018-05-15 06:38:05 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 4 Eclipse Genie

2020-05-05 07:56:00 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 5 Eclipse Genie

2022-04-26 14:29:32 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.