Bug 446236 - Issues with Valgrind 3.8.1 version, after compiler upgrade
Summary: Issues with Valgrind 3.8.1 version, after compiler upgrade
Status: RESOLVED WORKSFORME
Alias: None
Product: valgrind
Classification: Developer tools
Component: memcheck (show other bugs)
Version: 3.8.0
Platform: RedHat Enterprise Linux Other
: NOR major
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-11-29 12:22 UTC by amita dwivedi
Modified: 2023-03-19 03:45 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description amita dwivedi 2021-11-29 12:22:42 UTC
After below compiler upgrade, we are facing issues with valgrind logs. A process is getting created and seen crashing and then re-created. This is in loop. Please let me know if the new versions are supported?

  Tool	Old Version	             New Version
gcc	        4.7.2 (2012-06)	            8.2.0 (2018-07)
binutils	2.23.1 (2012-11)	            2.32 (2019-02)
glibc	2.17 (2012-12)	            2.23 (2016-02)
Comment 1 Tom Hughes 2021-11-29 12:55:20 UTC
We don't support or not support particular toolchains.

Of course a new compiler might generate new instructions that an old one didn't and that might include an instruction that a given version of valgrind doesn't know how to emulate but if that happens if will give full details of the problem when it exits.

If you want help you're going to need to provide the output from valgrind when it crashes so that we can diagnose the problem.
Comment 2 Julian Seward 2021-11-29 12:58:47 UTC
Also, if it really is 3.8.1 that you are using .. that is ancient and unsupported.
Try again with the most recent version, 3.18.1.
Comment 3 Paul Floyd 2021-11-29 17:02:07 UTC
And what exactly are the errors?
Comment 4 Paul Floyd 2023-02-17 08:58:12 UTC
Another one for the Bug Janitor
Comment 5 Bug Janitor Service 2023-03-04 03:45:48 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2023-03-19 03:45:44 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!