| Summary: | gcov stuck in infinite loop | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Olle Liljenzin <olle> | ||||
| Component: | gcc | Assignee: | Jakub Jelinek <jakub> | ||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | qe-baseos-tools-bugs | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.6 | CC: | law, mpolacek, olle, ovasik, tlavigne | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-02-10 13:28:41 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1056252 | ||||||
| Attachments: |
|
||||||
This is not something we are going to try and fix at this stage in the RHEL 5 lifecycle. However, this is still an issue for RHEL 6 and beyond, so I am moving this bug to the RHEL 6 product. 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 is "fixed" in gcov in 4.7/4.8/4.9, but then it says: t.gcno:version '401p', prefer '409e' gcov: out of memory allocating 7020434128 bytes after a total of 135168 bytes Presumably that's using t.gcno from the bug itself -- odds are the current tools aren't capable of interpreting the older gcov output file. Does it work if you regenerate the .gcda/.gcno files? (In reply to Jeff Law from comment #5) > Does it work if you regenerate the .gcda/.gcno files? I'm afraid I can't do that, because for that I'd need to run the application, but the attached sources don't contain main () ... Olle, We really need the sources so that we can ensure this bug is fully addressed. While we know that gcov isn't currently hanging with the data files you've provided, we still have concerns about whether or not this bug has really been fixed or has just gone latent. The only way to be certain is to verify with both the data files you've already provided and with the original source files. I'm sorry but I have moved to a new employment and now I don't have access to the code I used when reporting the bug. I could ask someone still working there for help, but they have probably upgraded both the source code and the build machines it was produced on. This problem showed up in one place in an application that was built from millions line of source code. I tried to scale it down to a small and isolated test case, but then the problem disappeared. That was the reason for providing a preprocessed source file that I can't reproduce now. Thanks Olle. I think I'll probably have someone dig deeper into the memory allocation failure to verify what's happening with that issue, but probably won't take it further than that. Obviously if you run into another case where it hangs, definitely let us know. |
Created attachment 492086 [details] test case to reproduce the bug Description of problem: gcov hangs on some input files Version-Release number of selected component (if applicable): gcc-4.1.2-50.el5, gcc44-4.4.4-13.el5 How reproducible: Always Steps to Reproduce: 1. download and unpack the attached tar file 2. cd gcov-bug 3. gcov -a t.cpp Actual results: gcov loops in accumulate_line_counts Expected results: Should create the file t.E.gcov