Hi
Hey Paul,
it's hard to say what could be wrong without more details. Testing 4.5.3
would be indeed a good idea to check if this misbehavior has already
been fixed.
I've started.
If not, you should try to get and post a stack trace of the infinite
loop, e.g. using gdb or pstack(1) ...
pstack is not very helpful:
#0 0x00000000412d22 in main ()
gdb is better
#0 accumulate_line_counts (argc=8, argv=0x7fffffffc7f8)
at /free/NEW_GNU_BUILD/devenv_g3_package/src/gcc-4.5.1/gcc/gcov.c:1737
#1 generate_results (argc=8, argv=0x7fffffffc7f8)
at /free/NEW_GNU_BUILD/devenv_g3_package/src/gcc-4.5.1/gcc/gcov.c:566
#2 main (argc=8, argv=0x7fffffffc7f8)
at /free/NEW_GNU_BUILD/devenv_g3_package/src/gcc-4.5.1/gcc/gcov.c:377
Which gcov options are you using, by the way?
lcov -c -d . -o sim.info
wich according to ps runs gcov with
gcov adms_search.gcda -o sim -b -c -a -p
Trying those options one at a time, -b -c -p pass, -a doesn't.
Looking at the man page, -a determines block counts within a line.
Thanks to our chronic macro abuse, we have some pretty enormous single
lines, so it is conceivable that I'm hitting a performance problem and
gcov isn't stuck in an infinite loop.
A+
Paul