X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-bounces using -f
Message-ID: <3CCD93EE.1CFCEB45@lml.ls.fi.upm.es>
Date: Mon, 29 Apr 2002 20:41:50 +0200
From: Manuel Collado <m DOT collado AT aaron DOT ls DOT fi DOT upm DOT es>
X-Mailer: Mozilla 4.75 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: comp.os.msdos.djgpp
Subject: gcov for gcc-3.0.x fails if not LFN support
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 138.100.10.20
X-Trace: 29 Apr 2002 20:45:10 +0100, 138.100.10.20
Lines: 26
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

I think I've found a small bug on DJGPP ports of gcov in gcc-3.0.3 and
gcc-3.0.4. According to the gcc README file, this newgroup is the place
for reporting DJGPP port bugs. If not, please let me know and point me
in the right direction.

The problem is that gcov is not able to create the output file for a
'name.ext' source file if LFN is not available. The generated name is
'name.ext.gcov', that breaks the 8+3 rule.

This problem don't arise in gcc-2.95.3. Looking at the sources, I see a
small code fragment for special handling of the output file name in
absence of LFN support that is present in 2.95.3 but not in 3.0.3 nor in
3.0.4 versions of gcc.

The problem shows up in my Windows NT 4.0 worksation system, but I
suppose it affect also any system with no LFN support. The easiest
workarount is to keep gcov.exe from gcc-2.95.3.

BTW, I have some ideas about how to handle generation of special
shortnames at DJGPP core and not at the application/utility level. Is it
ok to explain them here?

Thanks,
-- 
To reply by e-mail, please remove the extra dot
in the given address:  m.collado -> mcollado