Description of problem: Recent combination of lcov and gcc seems to be generating Out-of-memory! message instead of processing of .gcno files. On my other box this combination on same source base (lvm2 project) works well: (Has same version of lcov & gcc-4.6) 18617 write(1, "Processing thin/thin.gcno\n", 26) = 26 18617 open("/lvm2/lib/thin/thin.gcno", O_RDONLY) = 3 18617 ioctl(3, SNDCTL_TMR_TIMEBASE or SNDRV_TIMER_IOCTL_NEXT_DEVICE or TCGETS, 0x7fffaf218000) = -1 ENOTTY (Inappropriate ioctl for device) 18617 lseek(3, 0, SEEK_CUR) = 0 18617 fstat(3, {st_mode=S_IFREG|0664, st_size=26052, ...}) = 0 18617 fcntl(3, F_SETFD, FD_CLOEXEC) = 0 18617 read(3, "oncgR704\261m\17O\0\0\0\1\21\0\0\0\26\0\0\0\342\221_\370\254\242@H"..., 8192) = 8192 18617 mmap(NULL, 4848783360, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = -1 ENOMEM (Cannot allocate memory) 18617 brk(0) = 0x1ecc000 18617 brk(0x122ef8000) = 0x1ecc000 Version-Release number of selected component (if applicable): lcov-1.9-1.fc17.noarch gcc-4.7.0-0.10.fc17.x86_64 How reproducible: Steps to Reproduce: 1. build project that supports lcov (i.e. lvm2, configure with --enable-profiling) 2. run any command (i.e. lvs) 3. build lcov for project (make lcov) Actual results: Expected results: Additional info:
I've confirmed with lcov 1.9 and gcc 4.7 with a trivial 'Hello World'. Downgrading lcov does not help, nor does lcov from upstream CVS. Therefore it must be the gcc 4.6 -> 4.7 change, upsetting some assumption in lcov.
lcov-1.9-2.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/lcov-1.9-2.fc17
lcov-1.9-2.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/lcov-1.9-2.fc16
Package lcov-1.9-2.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing lcov-1.9-2.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-3611/lcov-1.9-2.fc17 then log in and leave karma (feedback).
Latest version lcov-1.9-2.fc18.noarch works for me, so I guess this bz could be closed as fixed.
lcov-1.9-2.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
lcov-1.9-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
I'm getting the same error with lcov-1.9.2 after a change in the code. Unfortunately, I cannot identify the change. What information is needed to debug this issue?
An interesting thing is that after cleaning up (git clean -dfx), it works correctly.
(In reply to comment #8) > I'm getting the same error with lcov-1.9.2 after a change in the code. > Unfortunately, I cannot identify the change. What information is needed > to debug this issue? I am actually getting the same error using lcov 1.10. I am using gcc 4.7.2 on Fedora 17 (64 bit). Originally I was using lcov 1.7, and the error was always produced. Now, with 1.10 is less regular. How can I help?
(In reply to comment #10) > (In reply to comment #8) > > I'm getting the same error with lcov-1.9.2 after a change in the code. > > Unfortunately, I cannot identify the change. What information is needed > > to debug this issue? > > I am actually getting the same error using lcov 1.10. > > I am using gcc 4.7.2 on Fedora 17 (64 bit). > Originally I was using lcov 1.7, and the error was always produced. > Now, with 1.10 is less regular. > > How can I help? I am not too sure any more. Maybe it was a corrupted file. Rebuilt and it works, will keep you posted.