Bug 730303
| Summary: | Need to increase VG_N_SEGNAMES | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jon Masters <jcm> |
| Component: | valgrind | Assignee: | Mark Wielaard <mjw> |
| Status: | CLOSED ERRATA | QA Contact: | qe-baseos-tools-bugs |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.1 | CC: | fche, mcermak, mfranc, mjw, mnewsome, pmuller, todoleza |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | valgrind-3.8.1-3.1.el6 | Doc Type: | Bug Fix |
| Doc Text: |
Previous versions of valgrind might report "Valgrind: FATAL: VG_N_SEGNAMES is too low." when running larger (C++) programs under valgrind. This version has increased the compile time constants VG_N_SEGMENTS to 50000 and VG_N_SEGNAMES to 25000 to prevent this error. Upstream description here: https://bugs.kde.org/show_bug.cgi?id=164485
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-02-21 08:50:53 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Jon Masters
2011-08-12 12:18:16 UTC
This is already tracked by upstream bugzilla. This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4. Another instance/reproducer:
$ valgrind -q stap -v -l 'module("*").function("*_exit")'
Pass 1: parsed user script and 99 library script(s) using 525708virt/314040res/4068shr/338080data kb, in 8820usr/180sys/9060real ms.
--12587:0:aspacem Valgrind: FATAL: VG_N_SEGNAMES is too low.
--12587:0:aspacem Increase it and rebuild. Exiting now.
The upstream setting of VG_N_SEGMENTS and VG_N_SEGNAMES have been kept low to support devices with just 512MB of memory that run large C++ applications under valgrind anyway. With the current upstream setting of 5000 for VG_N_SEGMENTS and 1000 for VG_N_SEGNAMES the static segnames[] and nsegments[] take up ~1.2MB. For server and workstation machines it should be fine to increase these (suggested values VG_N_SEGMENTS 50000 and VG_N_SEGNAMES 25000) to make these use up to ~26MB.
Note: above reproducer will take a couple of minutes to complete under valgrind (with a patch to increase VG_N_SEGMENTS and VG_N_SEGNAMES).
scratch build available Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-0347.html |