Mail Archives: djgpp/2001/03/13/04:56:33
Manuel Collado <m DOT collado AT fi DOT upm DOT es> wrote:
[...]
> Gcov is described in GCC info files in DJGPP distributions, but the
> executable doesn't appear in the bin directory.
I tackled that problem back in May 2000. Gcov and the machinery inside
GCC itself that feeds it have (well: had) two kinds of problems
running in a DJGPP environment:
1) text/binary file I/O. The sources hadn't been made portable to
filesystems where binary files need "rb" or "wb" file handling modes. That
was easily patched.
2) long filenames. The filenames generated by gcov are
generally compatible with the 8.3 restrictions:
foo.c --> foo.bb
foo.bbg
foo.da
--> foo.c.gcov
It's the latter that causes problems. And some more serious ones are
lurking, if you used #include files with executable code in them
(which means just about every single C++ class header out there, with
their inlined methods :-()
I had sent a small patch to fix 1), to the DJGPP workers list, back
then, and if memory serves, the DJGPP GCC maintainer then agreed to
use that patch for all future builds of DJGPP GCC packages. You can
find it in the djgpp-workers archive, using this message-id to search
for: <Pine DOT LNX DOT 4 DOT 10 DOT 10005021912140 DOT 496-200000 AT acp3bf>. It's in a
thread under subject 'gcc 3.0'.
--
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.
- Raw text -