From: Hans-Bernhard Broeker Newsgroups: comp.os.msdos.djgpp Subject: Re: Looking for gcov Date: 13 Mar 2001 09:46:31 GMT Organization: Aachen University of Technology (RWTH) Lines: 35 Message-ID: <98kq9n$air$1@nets3.rz.RWTH-Aachen.DE> References: <3AAD1268 DOT 50A96ED2 AT fi DOT upm DOT es> NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de X-Trace: nets3.rz.RWTH-Aachen.DE 984476791 10843 137.226.32.75 (13 Mar 2001 09:46:31 GMT) X-Complaints-To: abuse AT rwth-aachen DOT de NNTP-Posting-Date: 13 Mar 2001 09:46:31 GMT Originator: broeker@ To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Manuel Collado 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: . 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.