| Summary: | glibc version is baked into default suppressions file at Valgrind build time. | ||
|---|---|---|---|
| Product: | [Developer tools] valgrind | Reporter: | Evgeniy Stepanov <eugeni.stepanov> |
| Component: | general | Assignee: | Julian Seward <jseward> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | pjfloyd |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Unlisted Binaries | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | A straightforward fix: obtain the glibc major version from configure.in and substitute it ingo glibc.X.X.supp.in | ||
|
Description
Evgeniy Stepanov
2010-10-07 10:38:35 UTC
Created attachment 52332 [details]
A straightforward fix: obtain the glibc major version from configure.in and substitute it ingo glibc.X.X.supp.in
Honestly, having the same build work across multiple different glibc versions has never been a design goal. We've always said "build it on the platform you intend to use it on." I don't think that this is a good idea. Certainly for FreeBSD and macOS trying to mix the build version and test version OS is a bad idea. If you really need to have a different suppression file you can always produce suppression files for the different OSes and use --suppressions= |