From: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
To: <djgpp-workers AT delorie DOT com>
Subject: RE: Backslashes in debug info
Date: Sat, 6 Jan 2001 18:56:39 +0100
Message-ID: <NEBBIOJNGMKPNOBKHCGHCEFLCAAA.tim.van.holder@pandora.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-reply-to: <9003-Sat06Jan2001111535+0200-eliz@is.elta.co.il>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id MAA03212
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> I think I've found a bug in GCC: it doesn't support backslashes in
> file names when generating debug info.
I'm fairly sure it's a problem with libbfd/binutils (try gcc -S and
see what is emitted in the assembly file).
I thought this had already been fixed though. If not, it's probably
an oversight (I know several places in bfd were support for DOS
paths was added). Did you try binutils 2.10.1 too?
Also, I don't see this 14-char limitation with -gcoff; I tried
-gcoff3, -gcoff, -g and -gstabs+3 - all objects produced had the
full pathname (non-truncated; and it was 51 chars).