Date:	Sun, 7 Jan 2001 11:33:49 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	"Mark E." <snowball3 AT bigfoot DOT com>
cc:	djgpp-workers AT delorie DOT com
Subject:	RE: Backslashes in debug info
In-Reply-To:	<3A5726E8.7603.3A7B7@localhost>
Message-ID:	<Pine.SUN.3.91.1010107112750.21289R-100000@is>
MIME-Version:	1.0
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

On Sat, 6 Jan 2001, Mark E. wrote:

> > > 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
> 
> It is. I just posted a fix for stabs.

Is this the URL for the patch you referred to:

  http://sources.redhat.com/ml/binutils/2001-01/msg00083.html

?  If so, then isn't it better to convert all backslashes to forward 
slashes in debug info?  I think GDB might puke on backslashes, because 
the format spec for debug info calls for forward slashes.

(Actually, this thread was born because someone posted a patch on the GDB 
mailing list which depended on forward slashes in file names recorded in 
debug info.  The patch was not an exception: all the symtab-related 
modules in GDB are replete with literal '/'s.  I asked on the GDB list 
about the backslashes and got replied that they should be converted.  I 
then tried forcing DOS-style file names with backslashes with DJGPP tools 
and got the results with which I started this thread.)

- Raw text -